Lines Matching refs:release
11 This file intends to document the process of managing a Xen release. It is
16 # Xen release cycle
19 June and the beginning of December. The actual release date depends on a lot
22 We can roughly divide one release into two periods. The development period
30 for the release should be posted -- it is normally called the "last posting
43 * the anticipated release date is 2017 December 7
45 # The different roles in a Xen release
49 A trusted developer in the community that owns the release process. The major
50 goal of the Release Manager is to make sure a Xen release has high quality
55 release. He or she is expected to keep track of issues, arrange RCs,
106 release announcement. The Release Manager should be absolutely sure the
107 release is going out on a particular date before giving them the signal to
111 # What happens during a release
116 release, the major work items and any other information the Release Manager
159 Contributors to gather a list of features for the release. Discuss the
161 release, write a blog post for the release.
165 be done on a public mailing list, to minimize the risk of release related
166 media stories being published before the release date.
169 release, companies providing supporting quotes for the press release and
171 the press release in private.
177 4. The Community Manager will create release related documentation such as
179 accessible via a release category. This can be done in public.
182 press release (1-2 weeks before the release).
194 3. Negotiate release date options with PR personnel. Typically we need 3-4
199 4. Select the release date.
215 release deliverables (tags and tarballs - will usually be in place the day
216 before the release). At this point, PR collateral will be sent to reporters
217 (typically 2-3 working days before the release date) and we cannot undo
219 acceptable to make a xen-devel@ announcement *before* the PR release date
220 (blog, xen-announce@, press release).
232 If there is a new Release Manager for the next release, make sure the
258 https://downloads.xenproject.org/release/xen/X.Y.0-rcZ/xen-X.Y.0-rcZ.tar.gz
261 https://downloads.xenproject.org/release/xen/X.Y.0-rcZ/xen-X.Y.0-rcZ.tar.gz.sig
279 The tree is in good state. No release ack is needed before RcX. Please commit
320 included for the release, please make sure they are posted for the first
334 included for the release, please make sure they are committed by $DATE.
364 A summary for X.Y release documents can be found at:
372 Thanks everyone who contributed to this release. This release would
387 # ./status-release.sh | formail -f -s /usr/sbin/ssmtp -bm -t
551 We now adopt a fixed cut-off date scheme. We will release twice a
562 into next release.