From: Jason Rumney <jasonr@gnu.org>
Cc: "'Eli Zaretskii'" <eliz@is.elta.co.il>, emacs-devel@gnu.org
Subject: Re: emacs 21.2
Date: 22 Mar 2002 19:38:13 +0000 [thread overview]
Message-ID: <m3k7s41jh6.fsf@nyaumo.btinternet.com> (raw)
In-Reply-To: <FC3DA3DC8D4AD311AB910020352A8FDC0BC62C82@eagle.midas-kapiti.com>
"Marshall, Simon" <simon.marshall@misys.com> writes:
> 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.
21.2 does fix some known serious bugs. But in each case, the chance of
the change causing its own new problems has to be balanced against the
problems it fixes. If we waited until EVERYTHING was fixed, we would
never release a version of Emacs again.
> Are you saying that, from the beginning, only minor fixes would be
> going in 21.2? What was the point of that?
Minor fixes generally don't cause problems, they only fix them. Major
fixes come with their own set of problems. Since 21.1 was a major
release with many new features, from the beginning it was thought that
a bugfix release would be needed. I think more bugs were expected in
21.1 than were actually found, so perhaps that is why this release may
seem unnecessary to some people.
--
Jason Rumney
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-22 19:38 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
2002-03-22 17:45 ` Eli Zaretskii
2002-03-22 19:38 ` Jason Rumney [this message]
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=m3k7s41jh6.fsf@nyaumo.btinternet.com \
--to=jasonr@gnu.org \
--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).