From: Eli Zaretskii <eliz@gnu.org>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: alexott@gmail.com, emacs-devel@gnu.org, storm@cua.dk, jasonr@gnu.org
Subject: Re: when emacs 22.1 release will ready?
Date: Mon, 30 Apr 2007 22:10:38 +0300 [thread overview]
Message-ID: <u8xc9wudt.fsf@gnu.org> (raw)
In-Reply-To: <4635BCB6.9060108@gmail.com> (lennart.borgman@gmail.com)
> Date: Mon, 30 Apr 2007 11:53:58 +0200
> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
> Cc: Alex Ott <alexott@gmail.com>, emacs-devel@gnu.org,
> "Kim F. Storm" <storm@cua.dk>
>
> > The quality of Emacs hasn't changed considerably over the past 3 years.
> > What would change it is to do a proper pretest cycle where only
> > regressions are fixed with the aim of reaching zero code changes after a
> > few pretest releases and releasing at that point.
>
> But how can you be sure that the changes does not cause new regressions
> without some kind of more automatic testing (like unit tests then)?
Jason said ``zero code changes''. Zero changes can never cause any
regressions.
next prev parent reply other threads:[~2007-04-30 19:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 20:37 when emacs 22.1 release will ready? Alex Ott
2007-04-30 9:21 ` Kim F. Storm
2007-04-30 9:33 ` Lennart Borgman (gmail)
2007-04-30 9:38 ` Jason Rumney
2007-04-30 9:53 ` Lennart Borgman (gmail)
2007-04-30 19:10 ` Eli Zaretskii [this message]
2007-04-30 21:30 ` Lennart Borgman (gmail)
2007-04-30 23:29 ` Juanma Barranquero
2007-04-30 9:56 ` Thomas Hühn
2007-04-30 10:18 ` Lennart Borgman (gmail)
2007-04-30 10:15 ` joakim
2007-04-30 10:25 ` Lennart Borgman (gmail)
2007-04-30 22:10 ` Richard Stallman
2007-04-30 15:18 ` unit testing [was Re: when emacs 22.1 release will ready?] Stephen J. Turnbull
2007-04-30 10:09 ` when emacs 22.1 release will ready? Leo
2007-04-30 10:23 ` Lennart Borgman (gmail)
2007-04-30 10:37 ` Leo
2007-04-30 11:29 ` Thien-Thi Nguyen
2007-04-30 15:20 ` Chong Yidong
2007-04-30 23:26 ` Leo
2007-04-30 22:09 ` 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=u8xc9wudt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alexott@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=storm@cua.dk \
/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).