Re: [Xen-devel] [DOCDAY] Maintenance Release Policy

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2012-11-26 at 16:37 +0000, Jan Beulich wrote:
> >>> On 26.11.12 at 16:58, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:

> > Changesets are nominated for inclusion in the stable branch by making a
> > request to the stable maintainer on xen-devel either by noting it as
> > such in the submission of the original patch to xen-unstable or by a
> > subsequent explicit email to xen-devel.
> 
> I think we should explicitly require the person expected to do the
> backport to be Cc-ed; I for myself don't get around to read _all_
> mails on xen-devel, and hence with a badly chosen subject it is not
> impossible (albeit also not likely) for me to miss such a request
> otherwise.
> 
> Furthermore, the branch maintainer should imo explicitly be given
> discretion to pull in patches without explicit request on the list

How about this, I don't think we need to explicitly consider the "please
revert it" case -- should be self evident?

8<----------------------------------------

Changesets are included in the stable branch at the discretion of the
branch maintainer.

As well as changesets identified by the branch maintainer as being suitable
for backport changes can also be nominated for inclusion in the stable
branch by making a request to the stable maintainer on xen-devel
either by noting it as such in the submission of the original patch to
xen-unstable or by a subsequent explicit email to xen-devel. Such
requests should be copied to the relevant stable maintainer. In
addition as part of the the stable release process the stable
maintainer will send one or more requests to xen-devel soliciting
suggestions for patches which should be included.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel