ReleaseTaskSignup

Differences between revisions 10 and 13 (spanning 3 versions)
Revision 10 as of 2016-01-26 20:42:20
Size: 1265
Editor: wxl
Comment: adding alpha 2 info
Revision 13 as of 2016-01-29 20:30:36
Size: 1479
Editor: wxl
Comment: changed trusty date according to https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule?action=diff&rev1=16&rev2=17
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

### don't delete this as this is how community release managers can come to understand what they're signing up for!
More information about these roles can be found at CommunityMilestoneProcess.
Line 6: Line 9:
|| [[XenialXerus/Alpha1 | 16.04 Alpha 1]] || January 4, 2016 || AdamConrad || [[WalterLapchynski]] || flavor contacts ||
|| 16.04 Alpha 2 ||
January 28, 2016 || SteveLangasek || [[WalterLapchynski]]/[[MartinWimpress]] || flavor contacts ||
|| 14.04.4 || February 4, 2016 || AdamConrad || || ||
|| [[XenialXerus/Alpha1 | 16.04 Alpha 1]] || January 4, 2016 || AdamConrad || WalterLapchynski || flavor contacts ||
||
[[XenialXerus/Alpha2 | 16.04 Alpha 2]] || January 28, 2016 || SteveLangasek || WalterLapchynski / MartinWimpress || flavor contacts ||
|| 14.04.4 || February 11, 2016 || AdamConrad || || ||

This signup sheet is to be used for planning release milestone tasks.

More information about these roles can be found at CommunityMilestoneProcess.

Milestones are based on: https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule and https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule

Milestone

Date

Image (Nusakan)
Engineering

Checklist Tracking

QA contact

16.04 Alpha 1

January 4, 2016

AdamConrad

WalterLapchynski

flavor contacts

16.04 Alpha 2

January 28, 2016

SteveLangasek

WalterLapchynski / MartinWimpress

flavor contacts

14.04.4

February 11, 2016

AdamConrad

16.04 Beta 1

February 25, 2016

flocculant

flavor contacts

16.04 Final Beta

March 24, 2016

AdamConrad

16.04 Release

April 21,2016

AdamConrad

When the archive is frozen, all members of the release team are expected to participate in bug fix reviews.

After FeatureFreeze, all members of the release team are expected to participate in Feature Freeze Exception reviews in their particular area of expertise.

After FinalBetaRelease, all members of the release team are expected to participate in Bug fix reviews in their particular area of expertise.

ZestyZapus/ReleaseTaskSignup (last edited 2017-02-17 15:13:00 by laney)