unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Updating release version to 22.1
Date: Tue, 08 Feb 2005 16:05:24 +0100	[thread overview]
Message-ID: <m31xbrum6j.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <x54qgngopy.fsf@lola.goethe.zz> (David Kastrup's message of "Tue, 08 Feb 2005 14:34:17 +0100")

David Kastrup <dak@gnu.org> writes:

>> So the CVS version will be updated to 22.1.-999, and pretests will be
>> numbered 22.1.-998 , 22.1.-997 , etc.
>>
> The numbering scheme may be geeky, but for all practical purposes it
> will cause trouble.  Consider this a strong objection.  I would
> appreciate getting at least the impression that the above reasons have
> registered before I get overridden.


We have discussed this before, and to the average user, our "current"
scheme where the cvs version to be released as 21.4 is named 21.3.50
is also very confusing.


I would much rather like to see some descriptive text in there, e.g.

  22.1.DEV

  22.1.PRE-1
  22.1.PRE-2

etc. when working towards a release 22.1

Subsequent bug fixes could be named

    22.1-1

So we could have

   22.1-1.DEV

   22.1-1.PRE-1

etc.

WDYT?


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  parent reply	other threads:[~2005-02-08 15:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 13:06 Updating release version to 22.1 Kim F. Storm
2005-02-08 13:34 ` David Kastrup
2005-02-08 14:46   ` Stefan Monnier
2005-02-08 15:05   ` Kim F. Storm [this message]
2005-02-08 15:43     ` Han Boetes
2005-02-08 16:24       ` David Kastrup
2005-02-08 15:58     ` David Kastrup
2005-02-08 20:12       ` Kim F. Storm
2005-02-08 21:18         ` Jérôme Marant
2005-02-08 22:34           ` David Kastrup
2005-02-08 22:38           ` Miles Bader
2005-02-09  0:17             ` Kim F. Storm
2005-02-09  0:32               ` David Kastrup
2005-02-09  1:21               ` Miles Bader
2005-02-09  8:30                 ` Kim F. Storm
2005-02-09  8:41                   ` Miles Bader
2005-02-09 11:23                     ` Kim F. Storm
2005-02-09 13:32                       ` Robert J. Chassell
2005-02-09 13:59                         ` David Kastrup
2005-02-09 14:15                         ` Jason Rumney
2005-02-10 18:39                       ` Richard Stallman
2005-02-10 21:49                         ` Kim F. Storm
2005-02-10 22:33                           ` Jérôme Marant
2005-02-10 22:52                             ` David Kastrup
2005-02-09 14:21                     ` Lennart Borgman
2005-02-09 14:56                       ` Kim F. Storm
2005-02-09  9:44                   ` Lute Kamstra
2005-02-09 10:54                     ` Kim F. Storm
2005-02-09 10:45                   ` David Kastrup
2005-02-09 10:52                     ` Miles Bader
2005-02-09 11:33                       ` Kim F. Storm
2005-02-10  6:01               ` Richard Stallman
2005-02-09 16:08 ` DONE: " Kim F. Storm
2005-02-09 16:32   ` David Kastrup
2005-02-09 17:39   ` Rob Browning
2005-02-10  6:01 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m31xbrum6j.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).