We have started to develop a release checklist (from the last Developer Meeting).
We need to enhance and agree on the checklist (ideally each step links to a more detailed process, and we're probably missing steps).
We should assign positions to names for each release so it is clear who does what.
We would like a "release coordinators" mailing list to, uhh, help coordinate the release.
We should adopt this checklist as a process, then we probably copy the page prior to each release with the names for each position.
Responsibility | Member(s) |
---|---|
release-lead | Bill Erickson |
release-notes-writer | now a community effort |
testers | |
bug-wrangler | Jason Stephenson |
web-team-member |
Responsibility | Member(s) |
---|---|
release-lead | Lebbeous Fogle-Weekley |
release-notes-writer | now a community effort |
testers | Michael Peters |
bug-wrangler | Jason Stephenson, Ben Shum |
web-team-member | Anoop Atre |
Responsibility | Member(s) |
---|---|
release-lead | Dan Scott |
release-notes-writer | Galen Charlton, Mike Rylander |
testers | |
bug-wrangler | Jason Stephenson |
web-team-member | Anoop Atre, Amy Terlaga |
Responsibility | Member(s) |
---|---|
release-lead | Jason Stephenson |
staff-client-packager | Jason Etheridge, Brian Feifarek, Ben Shum |
release-notes-writer | Anoop Atre, Mike Rylander |
testers | several |
bug-wrangler | Jason Stephenson |
web-team-member | Anoop Atre, Amy Terlaga |