From: David Kastrup <dak@gnu.org>
Cc: Juan LEON Lahoz Garcia <juanleon1@gmail.com>,
"Kim F. Storm" <storm@cua.dk>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: strange emacs 21.4 on ftp.gnu.org:/pub/gnu/emacs
Date: Mon, 07 Feb 2005 17:02:11 +0100 [thread overview]
Message-ID: <x54qgo73zw.fsf@lola.goethe.zz> (raw)
In-Reply-To: <x5d5vc754x.fsf@lola.goethe.zz> (David Kastrup's message of "Mon, 07 Feb 2005 16:37:34 +0100")
[Following up to myself]
David Kastrup <dak@gnu.org> writes:
> Answering the question is of secondary interest to answering the
> question how to deal with it. Personally, I'd like renaming this
> thing to 21.3a even though Kim has already stated he considers it
> unlikely that this might be a good idea/possible after the fact has
> been established.
[...]
> Given that, I recommend that we bother about what lies within our
> power, namely editing Emacs, as releasing it is not under our control.
> I propose that we now, where another renaming of everything has
> seemingly become necessary, decide to call the next major release
> 22.0, and also fix all corresponding documentation and :version
> strings (which are now completely fouled up) to refer to 22.0 instead.
>
> This will prevent
> a) us having to change all version strings again for the next major
> release more than once,
> b) us and third part package providers from looking like utter idiots
> when talking about release numbers, in case another security fix
> intervenes, invalidating all previously made statements and assurances
> again.
To underline that we would want to avoid having to do such a step
again, try a google search for "Emacs-21.4 -X-Emacs-21.4". That are
about 8430 pages/articles talking about Emacs-21.4. It is a safe bet
that at this point of time, pretty much none of them is talking about
what has been released as 21.4 by now.
Anybody volunteering for writing to the maintainers of those web pages
and articles? I am still not convinced that the 21.3a idea would not
be less painful in the long run, even though at the moment there exist
signed, though unannounced, 21.4 Emacs packages.
But again: it's not our call to make.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-02-07 16:02 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
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 [this message]
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
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=x54qgo73zw.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 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).