unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: How about a new pretest?
Date: Mon, 18 Dec 2006 22:38:58 +0200	[thread overview]
Message-ID: <uejqxlz19.fsf@gnu.org> (raw)
In-Reply-To: <17798.60984.342170.380829@kahikatea.snap.net.nz> (message from Nick Roberts on Tue, 19 Dec 2006 08:38:32 +1300)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Tue, 19 Dec 2006 08:38:32 +1300
> Cc: Juanma Barranquero <lekktu@gmail.com>, Emacs Devel <emacs-devel@gnu.org>
> 
> I think each pretest tarball should be a release candidate.

I'm not aware of such a policy.  A pretest should fix grave bugs, so
that people could use it in day-to-day work and make sure the bugs are
indeed fixed, and we should strive to make each new release cleaner
and less buggy than the previous one, but that's about it.

> So I can't see the point of a new pretest while bugs are still
> listed in FOR-RELEASE, other than to create the illusion that the
> release is getting nearer.

I don't see any serious bugs in today's FOR-RELEASE, and a cleaner
pretest _does_ make the release nearer, IMO.

  reply	other threads:[~2006-12-18 20:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 17:02 How about a new pretest? Juanma Barranquero
2006-12-18 17:54 ` Chong Yidong
2006-12-18 19:38   ` Nick Roberts
2006-12-18 20:38     ` Eli Zaretskii [this message]
2006-12-19  0:46     ` Juanma Barranquero
2006-12-18 20:13   ` Eli Zaretskii
2006-12-19 10:13     ` Kim F. Storm
2006-12-19 15:41       ` Kim F. Storm
2006-12-19 20:30         ` Chong Yidong
2006-12-19 22:37           ` Lennart Borgman
2006-12-19 22:40           ` Juanma Barranquero
2006-12-20 15:04           ` David Kastrup
2006-12-20 15:23             ` Juanma Barranquero
2006-12-20 13:01       ` Richard Stallman
2006-12-21 10:47         ` Jason Rumney
2006-12-21 13:41           ` Kim F. Storm
2006-12-21 23:18             ` Richard Stallman
2006-12-22  0:34               ` Kim F. Storm
2006-12-22 21:52                 ` Stefan Monnier
2006-12-23 20:13                 ` Richard Stallman
2006-12-25 13:30                   ` Kim F. Storm
2006-12-23 20:13                 ` Richard Stallman
2006-12-23 20:42                   ` Lennart Borgman
2006-12-24 17:09                     ` Richard Stallman
2006-12-24 17:22                       ` Lennart Borgman
2006-12-21 23:18           ` 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=uejqxlz19.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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).