unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs 21.4
Date: Tue, 08 Feb 2005 00:46:44 +0100	[thread overview]
Message-ID: <x5d5vc2asb.fsf@lola.goethe.zz> (raw)
In-Reply-To: <16903.63023.468339.184711@farnswood.snap.net.nz> (Nick Roberts's message of "Tue, 8 Feb 2005 12:13:51 +1300")

Nick Roberts <nickrob@snap.net.nz> writes:

>  > What needs to be done now?
>  > 
>  ...
>
>  > b) In the CVS version, the version number should likely get
>  > bumped to 22.0.50 instead of the current 21.3.50.  There is no
>  > sense in making it 21.4.50, anyhow, and it would be quite
>  > misleading to have it stay at 21.3.50, lower than the current
>  > released version.
>  > 
>  > c) all references to 21.4 need to be replaced by referring to
>  > 22.1 in our CVS.
>
>  ...
>
> Constructing such a plan only makes sense if you are prepared to
> accept that it might be ignored completely.

That's what point "e)" was for.  Anyway, this _is_ all about
minimizing the negative impact of a future potentially uncoordinated
release.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-02-07 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 20:50 Emacs 21.4 Richard Stallman
2005-02-07 22:42 ` David Kastrup
2005-02-07 23:13   ` Nick Roberts
2005-02-07 23:46     ` David Kastrup [this message]
2005-02-07 23:56   ` Miles Bader
2005-02-08  0:54     ` David Kastrup
2005-02-09  8:10   ` Richard Stallman
2005-02-09  8:10   ` Richard Stallman
2005-02-09  9:23     ` Miles Bader
2005-02-14  9:46 ` Yoichi NAKAYAMA
2005-02-15 17:28   ` Richard Stallman
2005-02-15 23:54     ` Yoichi NAKAYAMA
2005-02-16  7:11       ` Nick Roberts
2005-02-16  9:03         ` Yoichi NAKAYAMA
2005-02-17 10:35       ` Richard Stallman
2005-02-17 12:32         ` Francesco Potorti`

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=x5d5vc2asb.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).