all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Tue, 5 Nov 2002 08:05:29 +0200 (IST)	[thread overview]
Message-ID: <Pine.SUN.3.91.1021105075909.16406B-100000@is> (raw)
In-Reply-To: <200211041831.gA4IV0N24471@rum.cs.yale.edu>


On Mon, 4 Nov 2002, Stefan Monnier wrote:

> I obviously agree since I called for a feature freeze a few weeks
> (months?) back already.

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.

> I also think that 21.2 should have been taken
> from the trunk rather than from the RC branch and same thing for 21.3.

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.

> As Dave has explained the bug-fix release 21.3 will still be riddled with
> bugs

FWIW, I think ``riddled with bugs'' is a grave exaggeration.

> Maybe it will be a bit
> more stable from one particular point of view because it doesn't use any
> new code that might introduce new bugs, but I'm definitely not convinced
> that it outweighs the number of unfixed non-trivial bugs.

So do you really think that introduction of significant new features 
doesn't destabilize Emacs?

That is, do you suggest to skip branch releases because they are not more 
stable _in_principle_, or just because we are too inept to make them 
significantly more stable?

  reply	other threads:[~2002-11-05  6:05 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 [this message]
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
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

* 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.1021105075909.16406B-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 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.