From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Wed, 6 Nov 2002 08:00:16 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021106075444.960A-100000@is> (raw)
In-Reply-To: <200211052037.gA5KbGR30714@rum.cs.yale.edu>
On Tue, 5 Nov 2002, Stefan Monnier wrote:
> > > Even if we feature freeze it now, 21.4 will not be out before the end
> > > of 2003. I.e. long after 21.3.
> >
> > If you suggest to have two pretests running in parallel, I don't think
> > we can manage that with the available resources.
>
> feature-freeze != pretest.
Well, perhaps I misunderstood: what good is it to freeze the trunk unless
we start a pretest?
> But for 21.3, if it had been forked from the trunk rather than from RC could
> have been overall just as stable as 21.3 is.
IIRC, it was a judgement call, and at the time it sounded like we could
have 21.3 out the door in less than a month. Given that assumption, it's
not clear to me whether the decision was wrong. (To make it perfectly
clear, the decision was not mine.)
> So I just think that all releases should be forked from the trunk
> rather than from a previous release branch.
I could agree with that in principle. But in reality, it could happen
that the first release you make from the branch is not stable enough,
and that in the meantime the trunk got several new significant changes
that make it inappropriate for the next release.
next prev parent reply other threads:[~2002-11-06 6:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 16:16 21.2.90 pretest, 21.3, 21.4 Juanma Barranquero
2002-11-04 18:31 ` Stefan Monnier
2002-11-05 6:05 ` Eli Zaretskii
2002-11-05 7:02 ` Karl Eichwalder
2002-11-05 8:02 ` Juanma Barranquero
2002-11-05 18:40 ` Eli Zaretskii
2002-11-05 20:44 ` Karl Eichwalder
2002-11-06 6:29 ` Eli Zaretskii
2002-11-06 6:58 ` Karl Eichwalder
2002-11-06 14:18 ` Eli Zaretskii
2002-11-08 10:32 ` Kai Großjohann
2002-11-07 15:07 ` Richard Stallman
2002-11-05 8:02 ` Juanma Barranquero
2002-11-05 18:56 ` Eli Zaretskii
2002-11-05 12:02 ` Kai Großjohann
2002-11-05 19:00 ` Eli Zaretskii
2002-11-05 20:50 ` Stefan Monnier
2002-11-06 6:33 ` Eli Zaretskii
2002-11-06 12:40 ` Kim F. Storm
2002-11-06 12:55 ` Juanma Barranquero
2002-11-06 14:25 ` Eli Zaretskii
2002-11-06 14:49 ` Juanma Barranquero
2002-11-06 14:51 ` Miles Bader
2002-11-07 22:02 ` Francesco Potorti`
2002-11-07 8:08 ` (no subject) Kenichi Handa
2002-11-08 12:06 ` Richard Stallman
2002-11-07 22:00 ` 21.2.90 pretest, 21.3, 21.4 Francesco Potorti`
2002-11-09 11:54 ` Richard Stallman
2002-11-06 7:28 ` Kai Großjohann
2002-11-06 14:19 ` Eli Zaretskii
2002-11-06 7:49 ` Juanma Barranquero
2002-11-05 18:39 ` Stefan Monnier
2002-11-05 19:17 ` Eli Zaretskii
2002-11-05 20:37 ` Stefan Monnier
2002-11-06 6:00 ` Eli Zaretskii [this message]
2002-11-05 5:58 ` Eli Zaretskii
2002-11-05 7:56 ` Juanma Barranquero
2002-11-05 18:54 ` Eli Zaretskii
2002-11-05 20:40 ` Juanma Barranquero
2002-11-06 6:13 ` Eli Zaretskii
2002-11-06 4:49 ` Richard Stallman
2002-11-06 8:25 ` Juanma Barranquero
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 15:58 jasonr
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=Pine.SUN.3.91.1021106075444.960A-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@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).