Pretest schedule

Pretest schedule

[Chong Yidong]

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.

Re: Pretest schedule

[Kim F. Storm]

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 ?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: Pretest schedule

[Chong Yidong]

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.)

Re: Pretest schedule

[Kim F. Storm]

Chong Yidong <cyd@stupidchicken.com> writes:

>> 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.)

I just want to remove them before the final pretest so the pretest
is as close to the final release as possible.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: Pretest schedule

[Eli Zaretskii]

> From: storm@cua.dk (Kim F. Storm)
> Date: Mon, 09 Apr 2007 00:26:20 +0200
> Cc: emacs-devel@gnu.org
> 
> I just want to remove them before the final pretest so the pretest
> is as close to the final release as possible.

I think these markings should be removed as part of tarring the
release.  You cannot avoid creating a separate tarball anyway, since
at least the version numbers need to be changed, and release entries
added to all ChangeLog files.  So removing the NEWS marks now will
save maybe a few seconds of time, which isn't significant, certainly
not on the Grand Emacs Release Time Scale.

Re: Pretest schedule

[Kim F. Storm]

Eli Zaretskii <eliz@gnu.org> writes:

>  So removing the NEWS marks now will
> save maybe a few seconds of time, 

And catch the one that was inevitably left-over :-)

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: Pretest schedule

[Kim F. Storm]

storm@cua.dk (Kim F. Storm) writes:

> Should I clean-up the +++/--- lines in NEWS ?

I've looked through the NEWS entries, and the only ones which
are not marked with either +++ or --- are:

** BibTeX mode

do we need to document those changes anywhere?


** Mouse pointer features

??? (man)   

The mouse pointer shape in void text areas this is documented in the
lisp ref, but maybe we need to put anything into the user manual too.
But where?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: Pretest schedule

[Richard Stallman]

    I've looked through the NEWS entries, and the only ones which
    are not marked with either +++ or --- are:

    ** BibTeX mode

    do we need to document those changes anywhere?

We don't seem to cover BibTeX mode in the manuals in Emacs, so I guess
not.

    ** Mouse pointer features

    ??? (man)   

    The mouse pointer shape in void text areas this is documented in the
    lisp ref, but maybe we need to put anything into the user manual too.
    But where?

Those all seem to be about Lisp programming, so I see no need
to mention it anywhere in the Emacs manual.

I updated NEWS to indicate this.  Thanks.

Re: Pretest schedule

[Richard Stallman]

    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.

This plan looks realistic to me.

Re: Pretest schedule

[Stefan Monnier]

> 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.

If by "cut the Emacs 22 CVS branch" you mean

    cvs tag EMACS_22_BASE
    cvs tag -b EMACS_22_RC

then I fully agree.


        Stefan

Re: Pretest schedule

[Juanma Barranquero]

On 4/8/07, Chong Yidong <cyd@stupidchicken.com> wrote:

> 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.

Are we still more or less on track for branching today* and releasing
on April, 23*?

             Juanma


*: +n days, n being some small non-negative integer.

Re: Pretest schedule

[Chong Yidong]

"Juanma Barranquero" <lekktu@gmail.com> writes:

> On 4/8/07, Chong Yidong <cyd@stupidchicken.com> wrote:
>
>> 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.
>
> Are we still more or less on track for branching today* and releasing
> on April, 23*?

If there are no objections, I will do this tonight (EST).

The main thing we have to worry about right now are the recent
show-paren-mode fixes; if people could help test show-paren-mode as
much as possible, it would be nice.

IMO, the remaining bug in FOR-RELEASE---support for multiline
nicknames in RCIRC---should not hold the release; it concerns a fringe
feature (using Bitlbee, an IRC-to-IM gateway) of a non-essential
package (RCIRC), and no fix seems readily available.

Re: Pretest schedule

[Richard Stallman]

I think Monday is a plausible time for making a branch for Emacs 22.

Re: Pretest schedule

[Miles Bader]

Chong Yidong <cyd@stupidchicken.com> writes:
> IMO, the remaining bug in FOR-RELEASE---support for multiline
> nicknames in RCIRC---should not hold the release; it concerns a fringe
> feature (using Bitlbee, an IRC-to-IM gateway) of a non-essential
> package (RCIRC), and no fix seems readily available.

Actually, rcirc+bitlbee+multi-line-messages work just fine, as long as
you use separate rcirc buffers for each user/conversation (instead of
multiplexing the "channel" buffer) -- and since this usage is closer to
conventional IM usage (AIM clients etc), I suspect most users of
rcirc+bitlbee do this anyway (I certainly do).

Indeed my objections to Nic's patch have to do with not screwing up this
usage.  I suspect the fix is probably simple enough, like simply using
Nic's change only in "channel" buffers, but for this release it's
probably good enough to document the problem and mention the easy
workaround (use separate conversation buffers); I'm not sure where to
document it though...

-Miles

-- 
The car has become... an article of dress without which we feel uncertain,
unclad, and incomplete.  [Marshall McLuhan, Understanding Media, 1964]

Re: Pretest schedule

[Glenn Morris]

Miles Bader wrote:

> Indeed my objections to Nic's patch have to do with not screwing up this
> usage.  I suspect the fix is probably simple enough, like simply using
> Nic's change only in "channel" buffers, but for this release it's
> probably good enough to document the problem and mention the easy
> workaround (use separate conversation buffers); I'm not sure where to
> document it though...

Stick it in PROBLEMS?

I moved this item for FOR-RELEASE to TODO.

Re: Pretest schedule

[Roland Winkler]

storm@cua.dk (Kim F. Storm) writes:
> > Should I clean-up the +++/--- lines in NEWS ?
> 
> I've looked through the NEWS entries, and the only ones which
> are not marked with either +++ or --- are:
> 
> ** BibTeX mode
> 
> do we need to document those changes anywhere?

I apologize for my ignorance: could someone please tell me what the
+++/--- lines in NEWS are about?

Thanks,

Roland
(maintainer of BibTeX mode)

Re: Pretest schedule

[Nick Roberts]

 > I apologize for my ignorance: could someone please tell me what the
 > +++/--- lines in NEWS are about?

They're explained at the top of the file:

 +++ indicates that the appropriate manual has already been updated.
 --- means no change in the manuals is called for.


-- 
Nick                                           http://www.inet.net.nz/~nickrob