Gnus development mailing list
 help / color / mirror / Atom feed
From: Didier Verna <didier@xemacs.org>
To: <ding@gnus.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Version numbers of unreleased stable and development versions
Date: Tue, 29 May 2007 09:21:28 +0200	[thread overview]
Message-ID: <muxr6p0umbr.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <v94plwj14l.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon\, 28 May 2007 19\:42\:34 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Mon, May 28 2007, Didier Verna wrote:
>
>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>>
>>> Releases (beta and devel) from Gnus repository and CVS versions:
>>>
>>> ,-----------------------------------------------------------------------.
>>> | Standalone | CVS     || No Gnus | CVS   | Date / notes                 |
>>> | Gnus vers. | v5-10   ||         | trunk |                              |
>>> | beta rel.  |         || devel   |       |                              |
>>> |------------|---------||---------|-------|------------------------------|
>>> |            | 5.10.8  ||         |       |                              |
>>> |            |         || 0.6     |       | 2007-05-01                   |
>>> |            | 5.10.8  ||         | 0.7   | today                        |
>>> | 5.10.9     |         || 0.9     |       | close to release of Emacs 22 |
>>> |            | 5.10.10 ||         | 0.10  |                              |
>>> | 5.10.11    |         || 0.11    |       | ?                            |
>>> |            | 5.10.12 ||         | 0.12  |                              |
>>> | 5.10.13    |         || 0.13    |       |                              |
>>> |            | 5.10.13 ||         | 0.14  |                              |
>>> `------------------------------------------------------------------------'
>>
>>         My .02: I've never understood why people like this kind of
>> numbering scheme. I find them so confusing and inconsistent (John uses
>> odd/even, Jack uses even/odd, you never know which one is what etc).
>
> One of the major points for this discussion was to distinguish CVS
> versions and released version.  Now, if a user has "5.10.8" you can't
> tell if its from 2006-04-11 or 2007-05-28, i.e. it's unclear which
> bugs should already be fixed in this version.

        We should have CVS tags in all files. But if you really want to
give explicit versions to CVS intermediate, then you can use a timestamp.


> Upto now we had/have:
>
> - final = in Emacs = { 5.9, 5.11, 5.13, ... } 
>
> - beta = standalone release = { 5.8.x, 5.10.x, ... }
>
> - development = (prefixed named versions = ) = { Oort Gnus 0.y, No
>   Gnus 0.y, ...)
>
> How do you suggest to apply your scheme to these Gnus versions (i.e. 
> fill the table from my message with your suggested version numbers)?

        Thanks for this table. I'm actually beginning to understand the
Gnus version numbering scheme now that we're about to change it ;-) I
can't quite answer your question because I still don't understand the
relation between No Gnus and Gnus 5.10.*. Perhaps I would, if the table
was presented as a graph of CVS branches. Besides, your table lacks any
stable realease of Gnus (I know, Gnus is never stable ;-).

But if this table means that we actually have *two* development branches
in parallel (the 5.10 and the trunk), then that's not the numbering
scheme which is broken; it's the development process ! (again, I'm not
quite sure but I fear this has something to do with GNU Emacs people
committing changes to Gnus in the GNU Emacs repository instead of the
Gnus CVS archive)


So here's a partial answer, assuming the next release of Gnus would be
6.0: the *only* place where development in beta stage occurs (or should
occur) could be numbered as:

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 ]

Gnus 6.0                        => Tagged stable release


And then, the trunk goes to Gnus 6.1 beta 1 cvs blabla, while the 6.0
branch occasionally gets bugfixes and goes Gnus 6.0.1 etc.



Now I'm waiting to see the light about this mysterious 5.10 ghost...


-- 
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



  reply	other threads:[~2007-05-29  7:21 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 [this message]
2007-05-31 19:01             ` Reiner Steib
2007-06-04  9:29               ` Didier Verna
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=muxr6p0umbr.fsf@uzeb.lrde.epita.fr \
    --to=didier@xemacs.org \
    --cc=ding@gnus.org \
    --cc=larsi@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).