unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marshall, Simon" <simon.marshall@misys.com>
Cc: emacs-devel@gnu.org
Subject: RE: emacs 21.2
Date: Fri, 22 Mar 2002 15:20:32 -0000	[thread overview]
Message-ID: <FC3DA3DC8D4AD311AB910020352A8FDC0BC62C82@eagle.midas-kapiti.com> (raw)

> I'm sorry to hear that.  From the v21.2 pretest experience, it sounds
> like the interest in trying the pretest versions has diminished lately
> in general.  If that is so, the adverse effects of that will certainly
> show in the long run in the quality of our releases.  I lament that
> tendency, and hope I'm dead wrong in my conclusions.
> 
> I wish people would understand that sometimes stability is more
> important than fixing some annoying misbehavior or adding new
> features.  I wish more people who read this list would participate in
> pretesting Emacs, even if the release under pretest is a minor bugfix.

I don't know if you meant to direct this comment at the emacs-devel list
only; I changed the recipients from emacs-pretesters when I brought this
up since I originally just wanted to understand the release policy.

If it was directed at pretesters, then, put yourself in my (a pretester)
shoes.  I spent a large amount of my own time tracking down problems
with the last pretest & coming up with some fixes & testing others'.  I
did it because I thought it would be worth it: I thought the next Emacs
release would fix those problems.  Why would I bother if fixes wouldn't
appear in the next release?  Why would I bother if I could just leave it
to the pretests after next (or some future) release?

> Of course, since there's a judgement call involved, everybody is
> welcome to step forward and argue for the changes they think should
> be included.  But if you don't speak up, I can't see how can we take
> your views into account.

I think it is difficult for pretesters to follow the release policy
(assuming that they know what it is---I didn't/don't) and make these
kinds of judgements.  I think it has to come down to the judgement of
you guys.

I think your release policy itself is wrong---assuming I know what it
is---I think the only reason to release a version that does not fix
serious but not necessarily fatal bugs is when a quick release is needed
because the previous release was broken.  I think 21.2 should have fixed
known serious bugs as well as addressed "stability" (however you define
that) issues.

To take your 2nd para above, you say "even if the release under pretest
is a minor bugfix".  What on Earth does this mean?  IMHO, and no
criticism should be taken by anyone at all, it had some serious
behaviour and performance bugs.  Are you saying that, from the
beginning, only minor fixes would be going in 21.2?  What was the point
of that?

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


         reply	other threads:[~2002-03-22 15:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 12:43 emacs 21.2 Marshall, Simon
2002-03-22 14:21 ` Eli Zaretskii
2002-03-22 15:20   ` Marshall, Simon [this message]
2002-03-22 16:36     ` Juanma Barranquero
2002-03-22 17:45     ` Eli Zaretskii
2002-03-22 19:38     ` Jason Rumney
2002-03-22 23:54     ` Miles Bader
2002-03-23  8:59       ` Eli Zaretskii
2002-03-23 16:15     ` Richard Stallman
2002-03-23  9:03   ` Per Abrahamsen
2002-03-23 10:12     ` Eli Zaretskii
2002-03-24 15:51     ` Richard Stallman
2002-03-24 18:04       ` Eli Zaretskii
2002-03-25 12:02         ` Richard Stallman
2002-03-25 19:45           ` Eli Zaretskii
2002-03-26 10:14             ` Werner LEMBERG
2002-03-28  4:55               ` Richard Stallman
2002-03-28  9:37                 ` Eli Zaretskii
2002-03-29 17:15                   ` Florian Weimer
2002-03-29 17:32                     ` Eli Zaretskii
2002-03-29 17:47                       ` Florian Weimer
2002-03-22 16:52 ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2002-03-22 17:34 Marshall, Simon
2002-03-22 18:47 ` Eli Zaretskii
2002-03-22 17:05 Marshall, Simon
2002-03-22  9:40 Marshall, Simon
2002-03-22 11:44 ` Eli Zaretskii
2002-03-23 16:13 ` 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=FC3DA3DC8D4AD311AB910020352A8FDC0BC62C82@eagle.midas-kapiti.com \
    --to=simon.marshall@misys.com \
    --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).