From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org, rms@gnu.org,
"Jérôme Marant" <jmarant@free.fr>,
miles@gnu.org
Subject: Re: Updating release version to 22.1
Date: Wed, 09 Feb 2005 09:30:42 +0100 [thread overview]
Message-ID: <m3zmyexhhp.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <fc339e4a050208172164e891be@mail.gmail.com> (Miles Bader's message of "Wed, 9 Feb 2005 10:21:22 +0900")
Miles Bader <snogglethorpe@gmail.com> writes:
> On Wed, 09 Feb 2005 01:17:30 +0100, Kim F. Storm <storm@cua.dk> wrote:
>> > On Tue, 08 Feb 2005 22:18:41 +0100, Jérôme Marant <jmarant@freefr> wrote:
>> >> What's the rational for not using 22.0.x for development versions?
>> >> It would be so much simpler ...
>>
>> Because it - IMO - is confusing.
>
> What, compared to all the other bizarro schemes being suggested here
> ("hey I know, let's make pre-releases _blue_, and real releases
> _green_!")? You've got to be kidding... please say you're kidding...
Not really!
The problem with our _current_ scheme is that even though we seem to want to
postpone the decision about exactly what number the next release gets, it
is recorded _NUMEROUS_ places all over the sources and other files
(in total, I had to change 21.4 to 22.1 in more than 500 places).
I don't want us to get into that mess again -- so I want a scheme
where the next release number is _fixed_ from the start.
This is easily achieved by _always_ using MM.1 (MM = 22,23,24...) for
releases from the trunk, and MM.N (N = 2,3,4...) for bugfixes from the
release branch (RC_MM_1).
Given that, it seems a little odd that the development version is
called something different from MM.1-something...
But ok, lets stick with 22.0.50 for now.
My primary concern is if some code tests specifically for MM.1 in some
way, e.g. "version >= MM.1" and the dev/pretest version is MM.0, then
we may not see a specific error until we update the version to MM.1
and release the software -- without EVER testing that it works
with the actual release number.
Sadly code _does_ test version numbers!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-02-09 8:30 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zmyexhhp.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=jmarant@free.fr \
--cc=miles@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 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.