From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Updating release version to 22.1
Date: Wed, 09 Feb 2005 14:15:51 +0000 [thread overview]
Message-ID: <420A1B17.5010707@gnu.org> (raw)
In-Reply-To: <m1CyrxI-0004QkC@rattlesnake.com>
[-- Attachment #1.1: Type: text/plain, Size: 968 bytes --]
Robert J. Chassell wrote:
>> because what occured is that an extra real release was added in
>>between the last real release and the designated next real release.
>>
>>
>
>Yes, consequently the designated next real release should be called
>21.5.
>
RMS has already stated that the next release from the trunk will be
22.1, and I think most developers agree with him, so it is not a useful
use of our time to continue discussing what the next release will be called.
Discussing what the pre-release and development version will be called
is marginally more useful, but I've yet to see anyone put forward a
suggestion that does not have as many drawbacks as the current system,
and it has wasted a lot of time now, so unless someone comes up with
something new that they've thought through themselves first, then it
must be about time to drop the discussion and stick with what we have,
which while not perfect has suited us well enough until now.
[-- Attachment #1.2: Type: text/html, Size: 1351 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2005-02-09 14:15 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
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 [this message]
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=420A1B17.5010707@gnu.org \
--to=jasonr@gnu.org \
--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).