Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Version numbers of unreleased stable and development versions (was: Inaccuracy in the documentation)
Date: Fri, 23 Mar 2007 19:17:12 +0100	[thread overview]
Message-ID: <v9fy7vkeon.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4modml1o3r.fsf@jpl.org>

On Thu, Mar 22 2007, Katsumi Yamaoka wrote:

>>>>>> In <87k5x9msyz.fsf@baldur.tsdh.de> Tassilo Horn wrote:
>
>> the first thing is that the Gnus docs state that it corresponds to No
>> Gnus 0.4. I think it has to be 0.5, right?
>
>> ,----[ (info "(gnus)Top") ]
>>|    This manual corresponds to No Gnus v0.4.
>> `----
>
> 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.

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>

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




  reply	other threads:[~2007-03-23 18:17 UTC|newest]

Thread overview: 12+ 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   ` Reiner Steib [this message]
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
2007-06-15 17:53                   ` Reiner Steib

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=v9fy7vkeon.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).