From: Miles Bader <miles@lsi.nec.co.jp>
Cc: pmr@pajato.com, emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Rmail mbox-format branch
Date: Fri, 10 Sep 2004 18:38:50 +0900 [thread overview]
Message-ID: <buoeklacvkl.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <01c49717$Blat.v2.2.2$402ab840@zahav.net.il> (Eli Zaretskii's message of "Fri, 10 Sep 2004 12:18:16 +0300")
"Eli Zaretskii" <eliz@gnu.org> writes:
> Experience shows that 21.4 will most probably be followed by a bugfix
> release 21.5, a month or two after 21.4 is out; if that happens, we
> cannot move 22.1 into a pretest before the bugfix release is out.
> Since we cannot know whether 21.4 will need a bugfix release, we will
> wait at least a month or so before we decide, which again doesn't
> allow 22.1 to start a pretest immediately.
What's wrong with using a branch for bugfixes in 21.4?
The point of keeping a pending release on the trunk is to make sure it
gets a lot of testing. If 21.4 is released, then it's gonna be
reasonably solid, so there seems little point to having it hang around
on the trunk Just In Case; using a branch to fix those bugs that creep
into the release (and which are deemed serious enough to warrant another
minor release) seems quite reasonable.
-Miles
--
`...the Soviet Union was sliding in to an economic collapse so comprehensive
that in the end its factories produced not goods but bads: finished products
less valuable than the raw materials they were made from.' [The Economist]
next prev parent reply other threads:[~2004-09-10 9:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 4:02 Rmail mbox-format branch Richard Stallman
2004-09-09 14:13 ` Stefan
2004-09-09 14:44 ` Paul Michael Reilly
2004-09-09 15:25 ` Stefan
2004-09-09 18:56 ` Eli Zaretskii
2004-09-09 22:19 ` Miles Bader
2004-09-10 7:36 ` Kim F. Storm
2004-09-10 9:18 ` Eli Zaretskii
2004-09-10 9:38 ` Miles Bader [this message]
2004-09-10 10:41 ` Kim F. Storm
2004-09-10 11:44 ` Eli Zaretskii
2004-09-10 11:36 ` Eli Zaretskii
2004-09-10 10:39 ` Kim F. Storm
2004-09-10 11:42 ` Eli Zaretskii
2004-09-10 12:38 ` Kim F. Storm
2004-09-10 16:17 ` Eli Zaretskii
2004-09-11 23:19 ` Kim F. Storm
2004-09-11 10:52 ` Richard Stallman
2004-09-11 11:17 ` Eli Zaretskii
2004-09-11 16:45 ` Kim F. Storm
2004-09-11 2:49 ` Luc Teirlinck
2004-09-11 18:46 ` Proof-reading manuals (was Re: Rmail mbox-format branch) Kim F. Storm
2004-09-15 1:12 ` Luc Teirlinck
2004-09-16 11:19 ` Richard Stallman
2004-09-18 22:06 ` Luc Teirlinck
2004-09-19 11:00 ` Richard Stallman
2004-09-19 16:29 ` Proof-reading manuals Kim F. Storm
2004-09-11 10:50 ` Rmail mbox-format branch Richard Stallman
2004-09-11 11:22 ` Eli Zaretskii
2004-09-11 16:57 ` Stefan
2004-09-13 6:59 ` Richard Stallman
2004-09-15 10:25 ` Thien-Thi Nguyen
2004-09-11 13:50 ` Robert J. Chassell
2004-09-13 23:04 ` Richard Stallman
2004-09-10 17:41 ` Richard Stallman
2004-09-10 20:27 ` Alex Schroeder
2004-09-12 9:09 ` 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=buoeklacvkl.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=pmr@pajato.com \
--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).