Kubuntu/ReleaseManagement: Difference between revisions
(→Release Team: stay in touch, early milestones) |
(be organized, change hierarchy a bit) |
||
| Line 3: | Line 3: | ||
'''TODO''' At time of writing, this is written from the perspective of a Lubuntu Release Manager. This is to say that some additional items may be missing. It will be enhanced through discussions with previous Kubuntu Release Managers. | '''TODO''' At time of writing, this is written from the perspective of a Lubuntu Release Manager. This is to say that some additional items may be missing. It will be enhanced through discussions with previous Kubuntu Release Managers. | ||
== | == Stay in Touch == | ||
First off, make sure to participate in the modes of communication for the [http://wiki.ubuntu.com/ReleaseTeam Release Team]. This will keep you up to date on what's going on. In particular, IRC is the primary mode of communication for keeping up to date with day to day business. Especially during milestones, it is essential to be here for announcements of respins or systemwide bugs. | |||
First off, make sure to participate in the modes of communication for the | |||
;IRC channel | ;IRC channel | ||
| Line 14: | Line 12: | ||
: [https://lists.ubuntu.com/mailman/listinfo/ubuntu-release [email protected]] | : [https://lists.ubuntu.com/mailman/listinfo/ubuntu-release [email protected]] | ||
=== | == Be Organized == | ||
Be aware of the [https://wiki.ubuntu.com/ReleaseSchedule release schedule], paying close attention to the older LTS releases. They get approximately five [https://wiki.ubuntu.com/PointReleaseProcess point releases], the cycle of which often overlaps parts of current release development cycles. | |||
== Help Out the Community == | |||
As a general rule the "canonical" Ubuntu releases (i.e. Desktop, Server, etc.) as opposed to the actual flavors do not participate in the milestone process until the last beta. Canonical will provide infrastucture to allow for 2 alphas and one other beta milestone, as well as someone to flip the switches on the appropriate servers. | As a general rule the "canonical" Ubuntu releases (i.e. Desktop, Server, etc.) as opposed to the actual flavors do not participate in the milestone process until the last beta. Canonical will provide infrastucture to allow for 2 alphas and one other beta milestone, as well as someone to flip the switches on the appropriate servers. | ||
| Line 20: | Line 22: | ||
However, it is up to flavors to coordinate amongst itself. The [https://wiki.ubuntu.com/CommunityMilestoneProcess Community Milestone Process] details how this is done. Essentially, one person signs up as point of contact for that particular milestone. They are responsible for coordinating with the other flavors and sending out the final release announcement. | However, it is up to flavors to coordinate amongst itself. The [https://wiki.ubuntu.com/CommunityMilestoneProcess Community Milestone Process] details how this is done. Essentially, one person signs up as point of contact for that particular milestone. They are responsible for coordinating with the other flavors and sending out the final release announcement. | ||
== | == Herd Cats == | ||
== | == Make Decisions == | ||
Revision as of 03:57, 14 November 2016
The purpose of this document is to outline the duties and responsibilities of the Kubuntu Release Manager.
TODO At time of writing, this is written from the perspective of a Lubuntu Release Manager. This is to say that some additional items may be missing. It will be enhanced through discussions with previous Kubuntu Release Managers.
Stay in Touch
First off, make sure to participate in the modes of communication for the Release Team. This will keep you up to date on what's going on. In particular, IRC is the primary mode of communication for keeping up to date with day to day business. Especially during milestones, it is essential to be here for announcements of respins or systemwide bugs.
- IRC channel
- #ubuntu-release on freenode
- mailing list
- [email protected]
Be Organized
Be aware of the release schedule, paying close attention to the older LTS releases. They get approximately five point releases, the cycle of which often overlaps parts of current release development cycles.
Help Out the Community
As a general rule the "canonical" Ubuntu releases (i.e. Desktop, Server, etc.) as opposed to the actual flavors do not participate in the milestone process until the last beta. Canonical will provide infrastucture to allow for 2 alphas and one other beta milestone, as well as someone to flip the switches on the appropriate servers.
However, it is up to flavors to coordinate amongst itself. The Community Milestone Process details how this is done. Essentially, one person signs up as point of contact for that particular milestone. They are responsible for coordinating with the other flavors and sending out the final release announcement.