From: Chong Yidong <cyd@stupidchicken.com>
To: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Pretest schedule
Date: Sun, 08 Apr 2007 18:10:13 -0400 [thread overview]
Message-ID: <871wiuo6uy.fsf@stupidchicken.com> (raw)
In-Reply-To: <m3veg6pn3n.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Sun\, 08 Apr 2007 23\:34\:04 +0200")
storm@cua.dk (Kim F. Storm) writes:
> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> I would like to propose the following plan for the 22.1 release.
>>
>> I will roll the 22.0.98 pretest tarball on Monday, April 16 (8 days
>> from now). I believe this should be the final pretest, unless a major
>> problem arises.
>>
>> If no major problems with the April 16 pretest come to light, we
>> should cut the Emacs 22 CVS branch on Friday, April 20, and release
>> Emacs 22.1 on Monday, April 23.
>
> That would be great!!
>
> Should I clean-up the +++/--- lines in NEWS ?
No. I think RMS wants to do some "last-minute updating on the
manuals" (I don't know what this entails). Anyway, removing the
+++/--- lines will take all of a second with a query-replace-regexp,
so let's not worry about that task.
(Not that we seem to have much else to do, at this point.)
next prev parent reply other threads:[~2007-04-08 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 14:21 Pretest schedule Chong Yidong
2007-04-08 21:34 ` Kim F. Storm
2007-04-08 22:10 ` Chong Yidong [this message]
2007-04-08 22:26 ` Kim F. Storm
2007-04-09 6:03 ` Eli Zaretskii
2007-04-10 10:55 ` Kim F. Storm
2007-04-08 22:24 ` Kim F. Storm
2007-04-09 15:42 ` Richard Stallman
2007-04-09 15:41 ` Richard Stallman
2007-04-09 19:19 ` Stefan Monnier
2007-04-20 12:57 ` Juanma Barranquero
2007-04-20 14:17 ` Chong Yidong
2007-04-21 14:30 ` Richard Stallman
2007-04-22 1:40 ` Miles Bader
2007-04-22 1:53 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2007-04-10 1:50 Roland Winkler
2007-04-10 2:18 ` Nick Roberts
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871wiuo6uy.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.