Re: Extensive changes during pretest

[Chong Yidong <cyd@stupidchicken.com>]

Eli Zaretskii <eliz@gnu.org> writes:

> Why are so many changes being checked-in so late in the pretest?  They
> don't seem to be bugfixes to me (see below).
>
> Would the head maintainers please state clear guidelines on what
> should and what should not be installed at this time?  In the absence
> of a formal procedure for reviewing patches before they are committed
> and/or for posting them after the commit, I think it's imperative we
> have clear and agreed-upon guidelines.

We're still working out how the release process is going to be
handled.

In the meantime, while I'm aware that maintainers such as Michael
McNamara (for verilog) and Alan Mackenzie (for CC mode) have
significant leeway for checkins affecting their parts of the code, Eli
is right: Emacs 22.2 is already in pretest, so such changes shouldn't
be made to the branch at this point in time.  At the very least,
please inform emacs-devel to make sure it doesn't clash with the
pretest.

For small safe bug fixes, do continue sending them directly into the
branch, as we're currently doing, for the moment.

New features should be going into the trunk; if you want to backport
it to Emacs 22, please wait till after 22.2 is released and propose
the backport on emacs-devel.

Where in doubt, email emacs-devel.

Thanks!