From: Juanma Barranquero <lektu@terra.es>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>, emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Tue, 05 Nov 2002 09:02:01 +0100 [thread overview]
Message-ID: <20021105085714.0CDB.LEKTU@terra.es> (raw)
In-Reply-To: <Pine.SUN.3.91.1021105075909.16406B-100000@is>
On Tue, 5 Nov 2002 08:05:29 +0200 (IST), Eli Zaretskii <eliz@is.elta.co.il> wrote:
> IMHO, it doesn't make sense to feature-freeze the trunk unless we decide
> not to release from the branch anymore. Since there was a decision to
> release 21.3 from the branch, the decision not to feature-freeze followed
> almost automatically.
OK, but then, as soon as 21.3 hits the streets, we *should* create a new
release branch, feature-freeze it and start pretesting it. If we want a
shinny new-features release sometime before 2004, I mean. And it's my
*strong* believe we should want it. Like it or not, users and developers
are more attracted if it seems there's movement. I'd bet people out
there things Emacs development is glacial.
> For 21.3, maybe. But for 21.2, I disagree. You effectively suggest to
> eliminate bugfix releases, which I think would be wrong: users will have
> no stable versions to rely upon.
I cannot talk on behalf of Steffan, but at least I, who started the
thread, *don't* suggest such a thing. I suggest schedules.
/L/e/k/t/u
next prev parent reply other threads:[~2002-11-05 8:02 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 [this message]
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
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=20021105085714.0CDB.LEKTU@terra.es \
--to=lektu@terra.es \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).