History: Release Team
Preview of version: 27
Ongoing responsibilities
- Set a general timeline for each release, according to our Version Lifecycle
- Pick a star name
- Decide When to branch
- Maintain list of regressions and follow-up to get resolved (triage, blockers management, etc)
- Coordinate with other teams to insure that each of the Contributions of each Team to the release process are covered
- Agree to an action plan which is on or linked from the release page, such as Tiki18
- These people know several months in advance what their responsibilities are and thus, have ample time to plan and improve the procedure (and make sure nothing happens in the development cycle which will jeopardize their part).
- Make a schedule on release page, such as Tiki15 and coordinate to make sure all relevant domains are upgraded appropriately to the newly created branch.
- Coordinate the actual various release runs (Alpha, Beta, RC)
- Decide when to release
For each release, a release coordinator, and two assistant release coordinators are picked. This should be done towards the beginning of the cycle, so for example, as soon as 19.0 is released, it's time to identify them for 20.0
| Version | Coordinator | Assistant(s) |
|---|---|---|
| 19 | Luis Henrique Fagundes | to be determined |
| 18 | Bernard Sfez / Tiki Specialist | Jonny Bradley, Luis Henrique Fagundes |
| 17 | Bernard Sfez / Tiki Specialist | Jonny Bradley |
| 16 | Bernard Sfez / Tiki Specialist | Jonny Bradley |
| 15 | Bernard Sfez / Tiki Specialist | Jonny Bradley |
Traditionally, people change roles for each release
- because it's time consuming
- so many people gain the experience
Projects
Requirements
➡️ Be in touch with the developments on your release. It's a mandatory to be subscribed to the SVN Mailing List for this, so you can catch up whilst you're away
➡️ Be available on IRC throughout the release cycle for assistance/support and co-ordination
➡️ Knowledge or background of software engineering, and especially with SVN
➡️ Taste of working with people. Self-sufficient release managers can end up working in isolation. Social skills are a plus, decent English is useful too.
➡️ Have a Linux computer so you can use our release scripts, and create the tar.gz files. See: How to release
➡️ Would be a good idea to be able to code PHP too, especially to fix any last minute showstoppers.
Who
Related links