[gnutls-help] gnutls 3.7.7

[Simon Josefsson]

Daiki Ueno <ueno at gnu.org> writes:

>>> Hello,
>>>
>>> did the Gnutls version number semantics change?
>>>
>>> Iirc for release in 3.x series at some point of time 3.n.m was declared
>>> stable and when 3.n+1 was branched off as next, i.e. there were stable
>>> releases of 3.0, 3.1, ….
>
> That seems to be the case.  For example, 3.4.0 was released as
> stable-next[1] and after a few iterations 3.4.x branch was marked as
> stable[2] while 3.5.x was in development in the git master branch.
>
> At some point during the 3.6.x cycle, however, the "next" concept has
> been abandoned[1], and afterwards we repurposed it for 3.7.x
> development.

Ah.  So instead of using an odd/even scheme we use a dynamic scheme
where we can change which branch are considered stable vs development by
changing RELEASES.md?  I don't care strongly, as long as the approach is
documented and possible to understand.

>> -|stable|3.6.x  |as needed       |
>> -|next  |3.7.x  |bi-monthly      |
>> +|stable|3.7.x  |as needed       |
>> +|next  |3.8.x  |bi-monthly      |
>
> Sounds good to me.  I guess all we need is to have a gnutls_3_7_x branch
> and proper documentation of the current versioning scheme :-)

So how about this patch?

/Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Doc-fix-about-version-numbers.patch
Type: text/x-diff
Size: 778 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnutls-help/attachments/20220906/50c6a5eb/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 255 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnutls-help/attachments/20220906/50c6a5eb/attachment.sig>