Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Gnus <ding@gnus.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Version numbers of unreleased stable and development versions
Date: Sat, 26 May 2007 10:21:06 +0200	[thread overview]
Message-ID: <v94pm0knbh.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <v9fy7vkeon.fsf_-_@marauder.physik.uni-ulm.de>

On Fri, Mar 23 2007, Reiner Steib wrote:

> On Thu, Mar 22 2007, Katsumi Yamaoka wrote:
[ Wrong version numbers in the manuals ]
>> So is the Message info.  I vote to making them synch to
>> `gnus-version', as well as the ones in the Emacs CVS and
>> the v5-10 branch.  It will make releasing new versions easy.
>
> Well, the Makefile rules (see "release-bump-version") I've added
> before releasing 5.10.8 already do the job automatically.  But Lars
> didn't seem to have used them for the release of No Gnus v0.5.

... and No Gnus 0.6.  ;-)

> Another point is, that we started some discussion about a new version
> number policy, but IIRC we didn't come to a final conclusion and/or
> nobody stepped forward to put into practice.
>
> ,----[ <news:m37j5vxvjv.fsf@quimbies.gnus.org> ]
> | Anyway, how about using an odd/even-numbered methodology?  The
> | odd-numbered ones are in CVS, and when a release is published, it gets
> | the next even number.  
> `----
>
> <http://thread.gmane.org/gmane.emacs.gnus.general/62634>
> <http://thread.gmane.org/gmane.emacs.gnus.general/62660>
> <http://search.gmane.org/?query=Version%20numbers%20of%20unreleased%20stable%20and%20development%20versions&group=gmane.emacs.gnus.general>

,----[ Lars in http://article.gmane.org/gmane.emacs.gnus.general/62660 ]
| Anyway, how about using an odd/even-numbered methodology?  The
| odd-numbered ones are in CVS, and when a release is published, it gets
| the next even number.  
`----

As the versions in Emacs (which are supposed to be the stable release
versions) have odd numbers (5.9, 5.11), it might be better to do it
the other way round: even = CVS (unrelease), odd = release.

Thus, we will have the following scheme...

In Emacs (final versions of Gnus):
  Emacs 21: Gnus 5.9
  Emacs 22: Gnus 5.11
  Emacs 23: Gnus 5.13
  ...

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

But I don't care too much whether we use odd/even or even/odd
(CVS/release) actually, but it would be nice to make a decision soon.
I'd volunteer to adjust the release-* rule in Makefile.in accordingly.

As the release of Emacs 22.1 seems to get really closer finally
(<http://thread.gmane.org/E1HrUMp-0007iw-FX%40fencepost.gnu.org>), it
would be nice to release a new 5.10.* soon after this.  I'd volunteer
to prepare the tar-balls etc.

Additionally, (as sketched in the table) I'd propose release trunk and
v5-10 at the same time (as we did for 5.10.8 and No 0.4) to have the
same bug fix level.

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



  reply	other threads:[~2007-05-26  8: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     ` Reiner Steib [this message]
2007-05-28  9:03       ` Version numbers of unreleased stable and development versions 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
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=v94pm0knbh.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).