Re: gnutls 3.7.7

Simon Josefsson <[email protected]> Tue, 06 Sep 2022 09:25:12 +0200
Newsgroups gmane.network.gnutls.general
Message-ID <[email protected]>
Daiki Ueno <[email protected]> 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

_______________________________________________
Gnutls-help mailing list
[email protected]
http://lists.gnupg.org/mailman/listinfo/gnutls-help
0001-Doc-fix-about-version-numbers.patch (text/x-diff, 778 B)
From 550b0c130151611e855a619862b3761dd90a8a83 Mon Sep 17 00:00:00 2001
From: Simon Josefsson <[email protected]>
Date: Fri, 2 Sep 2022 11:37:18 +0200
Subject: [PATCH] Doc fix about version numbers.

Signed-off-by: Simon Josefsson <[email protected]>
---
 RELEASES.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/RELEASES.md b/RELEASES.md
index 53360df3d..1e7024033 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -14,5 +14,7 @@ cases change the API.
 
 |Branch|Version|Release interval|
 |:----:|:-----:|:--------------:|
-|stable|3.6.x  |as needed       |
-|next  |3.7.x  |bi-monthly      |
+|stable|3.7.x  |as needed       |
+|next  |3.8.x  |bi-monthly      |
+
+We use the ideas of https://semver.org/ for deciding version numbers.
-- 
2.30.2
signature.asc (application/pgp-signature, 255 B)
-----BEGIN PGP SIGNATURE-----

iIoEARYIADIWIQSjzJyHC50xCrrUzy9RcisI/kdFogUCYxb12BQcc2ltb25Aam9z
ZWZzc29uLm9yZwAKCRBRcisI/kdFomwPAQDMYXtRI8R9Cu20VahrjqqCTXA4JfzK
26qqWKPZlE/+lAEAu/mYmQ5au3GJGm2K8Myvc9eVTN6cGseimXyNEz8dvAc=
=lASg
-----END PGP SIGNATURE-----