From: "Thomas Hühn" <newsgroups@thomas-huehn.de>
To: emacs-devel@gnu.org
Subject: Re: when emacs 22.1 release will ready?
Date: Mon, 30 Apr 2007 11:56:09 +0200 [thread overview]
Message-ID: <87ps5mmbie.fsf@mid.thomas-huehn.de> (raw)
In-Reply-To: 4635B7F9.8090909@gmail.com
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
> What do they do to keep control over the quality? I guess they are
> using a lot of unit testing for the kernel, or?
I suppose there are *a lot* more people trying out pre-release kernels
than CVS Emacs or pretest versions.
Another point why this pretest thing over the last weeks might have been
bad:
People don't take "this is our pretest tarball, please check it for
severe errors, this is our chance to find showstoppers before the
release" serious if there are a lot more of "this time it's for real"
pretest tarballs after that with no release in sight. That means that
pretest tarballs reach even less potential testers.
That's more psychology than anything else, but it might count
nevertheless.
Thomas
next prev parent reply other threads:[~2007-04-30 9:56 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
2007-04-30 21:30 ` Lennart Borgman (gmail)
2007-04-30 23:29 ` Juanma Barranquero
2007-04-30 9:56 ` Thomas Hühn [this message]
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=87ps5mmbie.fsf@mid.thomas-huehn.de \
--to=newsgroups@thomas-huehn.de \
--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).