unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Release schedule
Date: Sat, 21 Apr 2007 16:02:13 -0400	[thread overview]
Message-ID: <b0ejmdqywq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r6qdlecf.fsf@stupidchicken.com> (Chong Yidong's message of "Sat, 21 Apr 2007 15:25:20 -0400")

Chong Yidong wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
[...]
>> In that case, I think we should make another pretest.  We cannot just
>> release the code with untested patches that got installed since the
>> 22.0.98 pretest.
>>
>> Does anyone disagree?

Cleverly worded... :)

> On Monday, I will cut the branch and roll a candidate Emacs 22.1
> tarball.  If no immediate problems are found with that tarball, I
> think we can make that the official release.

This doesn't seem like a good idea to me. I suggest branching on
Monday, making an immediate final pretest from the branch, waiting a
few days (and not making _any_ changes unless Emacs is shown to
explode), then making a release.

I was hoping for a St George's day release, alas... :(

  reply	other threads:[~2007-04-21 20:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 21:53 Release schedule Richard Stallman
2007-04-21  3:38 ` Chong Yidong
2007-04-21 10:11 ` Eli Zaretskii
2007-04-21 19:25   ` Chong Yidong
2007-04-21 20:02     ` Glenn Morris [this message]
2007-04-21 20:14       ` Chong Yidong
2007-04-21 20:17         ` Glenn Morris
2007-04-21 22:31       ` Nick Roberts
2007-04-21 23:02         ` Glenn Morris
2007-04-22  3:08     ` Eli Zaretskii
2007-04-22  8:11       ` Juanma Barranquero
2007-04-22 10:33         ` Kim F. Storm
2007-04-22 11:13           ` David Kastrup
2007-04-23  3:48             ` Richard Stallman
2007-04-23  5:13               ` Stefan Monnier
2007-04-23  6:12                 ` David Kastrup
2007-04-22 11:51           ` Romain Francoise
2007-04-22 14:20       ` Chong Yidong
2007-04-22 22:56       ` Kenichi Handa
2007-04-22 16:35     ` Richard Stallman
2007-04-22 20:42       ` Eli Zaretskii

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=b0ejmdqywq.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).