[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] A document for Xen release management
On Tue, Jul 18, 2017 at 01:45:45PM +0100, Julien Grall wrote: > Hi Wei, > > Thank you for writing down the document :). > > On 17/07/17 16:09, Wei Liu wrote: > > It is agreed during the summit we should write down such document. Here > > is my attempt of doing so. > > > > We should probably commit something like this into xen.git so that it > > gets updated regularly. > > > > Comments are welcome. > > > > ----- > > > > % Xen Release Management > > % Wei Liu <<wei.liu2@xxxxxxxxxx>> > > % Revision 1 > > > > # Motivation > > > > Over the years we have had different people from different company signning > > up as the Release Manager of Xen. It would be rather wasteful if every new > > Release Manager has to go over everything and tripped over by the same > > mistakes again and again. > > > > This file intends to document the process of managing a Xen release. It is > > mainly written for Release Manager, but other roles (contributors, > > maintainers and committers) are also encouraged to read this document, so > > that they can have an idea what to expect from the Release Manager. > > > > # Xen release cycle > > > > The Xen hypervisor project now releases twice a year, at the beginning of > > June and the beginning of December. The actual release date depends on a lot > > of factors. > > Do we have a document detailing the release cycle (e.g last posting date, > hard code freeze...)? If not, would it be worth describing the current > cut-off scheme here? Sure. [...] > > release is going out on a particular date before giving them the signal to > > proceed, because there is a point of no return once they schedule a date > > with > > external reporters. > > > > # What happens during a release > > > > ## Development period > > > > Send out monthly update email. The email contains the timeline of the > > release, the major work items and any other information the Release Manager > > sees fit. Please consider adding a recurring event to your calendar. > > I would also add a paragraph to send remainder a week before at least and > "Last posting date" and maybe the "Hard code freeze"? > > How about: > > "Send out monthly update email. The email contains the timeline of the > release, the major work items and any other information the Release Manager > sees fit. Reminder should also be sent a week before important cut-off date > (e.g last posting date, hard code freeze). Please consider adding a > recurring even to your calendar.". > SGTM. [...] > > # Email templates > > > > ## RC emails > > > > > Hi all, > > > > > > Xen X.Y rcZ is tagged. You can check that out from xen.git: > > > > > > git://xenbits.xen.org/xen.git X.Y.0-rcZ > > > > > > For your convenience there is also a tarball at: > > > https://downloads.xenproject.org/release/xen/X.Y.0-rcZ/xen-X.Y.0-rcZ.tar.gz > > > > > > And the signature is at: > > > https://downloads.xenproject.org/release/xen/X.Y.0-rcZ/xen-X.Y.0-rcZ.tar.gz.sig > > > > > > Please send bug reports and test reports to > > > xen-devel@xxxxxxxxxxxxxxxxxxxx. > > > When sending bug reports, please CC relevant maintainers and me > > > (abc@xxxxxxx). > > > > > > As a reminder, there will be another Xen Test Day. > > > > > > See instructions on: URL_TO_TEST_INSTRUCTIONS > > I would consider to add the templates for "Development update" and maybe the > script? > Yeah, just paste in a stripped down version of the script you use here. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |