unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Cc: "'Eli Zaretskii'" <eliz@is.elta.co.il>, emacs-devel@gnu.org
Subject: Re: emacs 21.2
Date: Fri, 22 Mar 2002 17:36:48 +0100	[thread overview]
Message-ID: <20020322171444.835F.LEKTU@terra.es> (raw)
In-Reply-To: <FC3DA3DC8D4AD311AB910020352A8FDC0BC62C82@eagle.midas-kapiti.com>

Sorry for jumping in.

On Fri, 22 Mar 2002 15:20:32 -0000, "Marshall, Simon"
<simon.marshall@misys.com> wrote:

> 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?

If I understand you right, you're saying that you consider pretesting
valuable for you if it is going to help to solve ASAP the problems you
encounter/suffer.

Well, I certainly don't see it that way. To me being a pretester is more
like voluntarily giving a helping hand in ironing out the bugs of Emacs
in a general way. Whether any fixes are to be included in the next
release, or the next one after that, or perhaps deemed too difficult, or
not right, or whatever, is not my call to judge. Obviously I would
"fight" and argument if I was told that something I deem very important
is to be delayed... but I ultimately must trust those who have more
Emacs experience than I do. And I'm not talking just about technical
experience, but project management experience as well.

> 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.

src/ChangeLog contains 367 non-blank, non-header lines of log comments between
release 21.1 and 21.2. lisp/ChangeLog has 329. Not earthshaking, but
nothing "minor" about it.

IMHO, increasing stability without simultaneously increasing complexity
for the users who want to use Emacs without it changing a lot under
their feet is a good, sensible goal.

But I don't think Eli is saying that 21.2 was meant to be a "minor
bugfix" under any circunstances; more like "it is a necesary release even
if only has minor bugfixes". The point not being "serious bugfixes won't
go in", but "no unnecesary changes (of interface, new features, etc.)
will go in". If a bug needs a big fix, it probably does not increase
stability...

That's not to say that a single, serious bug wouldn't be reason enough
to release a version, though :)

All that's MHO and nothing more, of course :)

                                                           /L/e/k/t/u


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


  reply	other threads:[~2002-03-22 16:36 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
2002-03-22 16:36     ` Juanma Barranquero [this message]
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=20020322171444.835F.LEKTU@terra.es \
    --to=lektu@terra.es \
    --cc=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).