From: Didier Verna <didier@xemacs.org>
To: ding@gnus.org
Subject: Re: Version numbers of unreleased stable and development versions
Date: Mon, 04 Jun 2007 11:29:44 +0200 [thread overview]
Message-ID: <muxd50coynr.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <v94plshl75.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu\, 31 May 2007 21\:01\:02 +0200")
OK, here's what I finally understand:
- there's the development branch (the trunk) in CVS with the unstable version
- there's the stable branch in CVS
- there's ALSO a stable branch in GNU Emacs'CVS
and then,
- the unstable branch leads or should lead to official beta versions
from time to time
- BOTH stable branches should lead to official patchlevel versions from
time to time
- which in turn lead to official stable patchlevel releases.
So here's what I think would be the most human-readable version
numbering scheme:
In the trunk
============
Gnus 6.0 beta 1 cvs 2007-08-01
2007-08-02
..........
Gnus 6.0 beta 1 => Tagged beta release
Gnus 6.0 beta 2 cvs 2007-09-01
2007-09-02
..........
Gnus 6.0 beta 2 => Tagged beta release
[ etc, finally leading to Gnus 6.0 ]
In the stable branch
====================
(while the trunk gets Gnus 6.1 beta)
Gnus 6.0 => Tagged stable release
Gnus 6.0.1 cvs 2007-10-01
cvs 2007-10-02
..........
Gnus 6.0.1 => Tagged stable release
Gnus 6.0.2 cvs 2007-11-01
cvs 2007-11-02
..........
Gnus 6.0.2 => Tagged stable release
[ etc ]
In the GNU Emacs repository
===========================
Gnus 6.0.1 emacs cvs 2007-10-01
emacs cvs 2007-10-02
..........
Gnus 6.0.1
Gnus 6.0.2 emacs cvs 2007-11-01
emacs cvs 2007-11-02
..........
Gnus 6.0.2
[ etc ]
And of course, the stable patchlevel tags should be synchronized between
our repository and that of GNU Emacs.
So, to summarize:
Unstable versions are: Gnus <major>.<minor> beta <level>
Stable versions are: Gnus <major>.<minor>.<patchlevel>
For intermediate CVS versions, add: [emacs] cvs yyyy-mm-dd
This is verbose, but quite clear I think. One could also wish to be more
coherent between stable and beta numbering, in which case we could also
think of: Gnus <major>.<minor> patchlevel <number>
Wadya think ?
--
Read the Jazz Blog !! http://jazzblog.didierverna.com
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier@xemacs.org
next prev parent reply other threads:[~2007-06-04 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 11:13 Inaccuracy in the documentation Tassilo Horn
2007-03-22 12:04 ` Katsumi Yamaoka
2007-03-23 18:17 ` Version numbers of unreleased stable and development versions (was: Inaccuracy in the documentation) Reiner Steib
2007-05-26 8:21 ` Version numbers of unreleased stable and development versions Reiner Steib
2007-05-28 9:03 ` Didier Verna
2007-05-28 12:57 ` Zlatko Calusic
2007-05-28 17:42 ` Reiner Steib
2007-05-29 7:21 ` Didier Verna
2007-05-31 19:01 ` Reiner Steib
2007-06-04 9:29 ` Didier Verna [this message]
2007-06-13 18:50 ` Reiner Steib
2007-06-15 17:53 ` Reiner Steib
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 15:59 Reiner Steib
2006-04-11 18:14 ` Bill Wohler
2006-04-12 4:33 ` Lars Magne Ingebrigtsen
2006-04-12 22:54 ` Bill Wohler
2006-04-13 5:48 ` Lars Magne Ingebrigtsen
2006-04-13 6:49 ` Romain Francoise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=muxd50coynr.fsf@uzeb.lrde.epita.fr \
--to=didier@xemacs.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).