Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Version numbers of unreleased stable and development versions
Date: Wed, 13 Jun 2007 20:50:21 +0200	[thread overview]
Message-ID: <v9abv3g042.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <muxd50coynr.fsf@uzeb.lrde.epita.fr>

On Mon, Jun 04 2007, Didier Verna wrote:

> OK, here's what I finally understand:
>
> - there's the development branch (the trunk) in CVS with the unstable version

Correct.

> - there's the stable branch in CVS

Correct.

> - there's ALSO a stable branch in GNU Emacs'CVS

Correct.  But apart from version numbers and missing XEmacs-specific
files, the two are identical.

> and then,
>
> - the unstable branch leads or should lead to official beta versions
>   from time to time

Correct.  But Lars doesn't label these "beta".  "beta" is the label
for the standalone stable releases (5.10.x, ...).

> - BOTH stable branches should lead to official patchlevel versions from
>   time to time
> - which in turn lead to official stable patchlevel releases.

Correct.

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

(Maybe your 6.0 numbers were simply examples, but for the record: No
Gnus will probably become 5.12/5.13)

What would be the value of `gnus-continuum-version' (used for
`gnus-convert-old-newsrc')?

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

From a user perspective, it may be confusing to get the difference
between Gnus 6.0.1 and Gnus 6.0 beta 1.

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

A couple of years I suggested to add a third number to the Gnus
version in Emacs (22.1: 5.11.1, 22.2: 5.11.2, ...).  But Larsi and
others didn't think it's useful:
<http://thread.gmane.org/gmane.emacs.gnus.general/58421>.

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

Personally, I'm not convinced that this would be clearer than an
odd/even thingie.  I'm waiting for Lars to make a decision so that we
can apply the new scheme and make a new 5.10.x release now that Emacs
22.1 has been released.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2007-06-13 18:50 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
2007-06-13 18:50                 ` Reiner Steib [this message]
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=v9abv3g042.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).