From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Extensive changes during pretest
Date: Sat, 23 Feb 2008 16:06:06 -0800 [thread overview]
Message-ID: <200802240006.m1O0661s028563@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <87zltrra4u.fsf@stupidchicken.com> (Chong Yidong's message of "Sat, 23 Feb 2008 10:00:01 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> 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.
Why not have the up to date checkin policy for each branch in
FOR-RELEASE?
That way there's no ambiguity what is going on, and there's a single
place to check what it TRTD. A message on the mailing list is very easy
to miss...
next prev parent reply other threads:[~2008-02-24 0:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 11:40 Extensive changes during pretest Eli Zaretskii
2008-02-23 15:00 ` Chong Yidong
2008-02-23 17:58 ` Minor Gnus changes for EMACS 22.2 pretest (was: Extensive changes during pretest) Reiner Steib
2008-02-24 0:06 ` Dan Nicolaescu [this message]
2008-02-23 15:52 ` Extensive changes during pretest Stefan Monnier
2008-02-23 19:46 ` Glenn Morris
2008-02-23 21:13 ` Eli Zaretskii
2008-02-23 21:52 ` Alan Mackenzie
2008-02-24 4:18 ` Eli Zaretskii
2008-02-24 8:20 ` Alan Mackenzie
2008-02-24 19:31 ` Juri Linkov
2008-02-24 20:11 ` Alan Mackenzie
2008-02-24 19:38 ` Eli Zaretskii
2008-02-24 20:03 ` Alan Mackenzie
2008-02-24 20:09 ` Eli Zaretskii
2008-02-24 20:42 ` Alan Mackenzie
2008-02-24 21:52 ` Eli Zaretskii
2008-02-24 22:34 ` Alan Mackenzie
2008-02-24 0:53 ` Richard Stallman
2008-02-25 16:24 ` Michael McNamara
2008-02-25 19:54 ` Chong Yidong
2008-02-25 20:34 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802240006.m1O0661s028563@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.