all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Juan LEON Lahoz Garcia <juanleon1@gmail.com>,
	emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: strange emacs 21.4 on ftp.gnu.org:/pub/gnu/emacs
Date: Mon, 07 Feb 2005 17:40:57 +0100	[thread overview]
Message-ID: <x5zmyg5nmu.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87oeewl61w.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 07 Feb 2005 10:57:21 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> Am I the only one who finds himself very much surprised that even
>>> though he's a fairly active contributor and reads emacs-devel,
>>> emacs-pretest-bug, gnu.emacs.help, gnus.emacs.bug,
>>> gnu.emacs.announce, and a few more places, he has not seen any
>>> announcement (let alone discussion) of this new release?
>
>> This question is rhetorical.
>
> Partly.  But maybe I had missed the announcement/discussion.
>
>> It would not appear, however, that either of our opinions would have
>> any relevance, anyway, so we might just stop musing about such things.
> [...]
>> I propose that we now, where another renaming of everything has
>> seemingly become necessary, decide to call the next major release
>
> Your first two lines above should make it clear to you that the
> second two lines would be a waste of time.

The work to rename versions throughout a release to arrive at a
consistent set is nontrivial and nothing that I expect a single person
to do in the time frame for an emergency release such as the latest
one we have seen.  And an emergency release is unlikely to occur from
the trunk.

Under the premise that 21.4 as a release number is here to stay,
version numbers all over the trunk will have to be changed, again.
IIRC, it was a work of several days for a single volunteer last time.
This work is not immediately tied to a release.  If the release
system/scripts don't accommodate emergency releases like 21.3a, as
established facts make it appear, then it would seem that we better
keep 21.5 off from both announcements and code, as the number might be
needed sooner than anticipated.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-02-07 16:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 10:45 strange emacs 21.4 on ftp.gnu.org:/pub/gnu/emacs Juan LEON Lahoz Garcia
2005-02-07 11:52 ` Romain Francoise
2005-02-07 11:59 ` David Kastrup
2005-02-07 13:54   ` Juan LEON Lahoz Garcia
2005-02-07 14:35   ` Kim F. Storm
2005-02-07 15:05     ` Stefan Monnier
2005-02-07 15:33       ` Jan D.
2005-02-07 15:37       ` David Kastrup
2005-02-07 15:57         ` Stefan Monnier
2005-02-07 16:40           ` David Kastrup [this message]
2005-02-07 17:25             ` Stefan Monnier
2005-02-07 21:56             ` Jérôme Marant
2005-02-07 22:44               ` David Kastrup
2005-02-08  8:20                 ` Jérôme Marant
2005-02-07 16:02         ` David Kastrup
2005-02-07 16:11       ` Kim F. Storm
2005-02-07 20:24       ` Eli Zaretskii
2005-02-07 20:42         ` Stefan Monnier
2005-02-08 11:46   ` 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

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

  git send-email \
    --in-reply-to=x5zmyg5nmu.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juanleon1@gmail.com \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.