Loading...
 
Skip to main content

History: Release Team

Preview of version: 22


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 Release Roles 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

Unable to load the jQuery Sortable Tables feature.


Traditionally, people change roles for each release

  • because it's time consuming
  • so many people gain the experience

Projects

Requirements

note: some of these should be moved to the Packaging

➡️ 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.

Related links

Related

alias

History

Advanced
Information Version
luciash d' being 🧙 38
View
Roberto Kirschbaum 37
View
Roberto Kirschbaum 36
View
Roberto Kirschbaum 35
View
Roberto Kirschbaum 34
View
Marc Laporte Unfortunately... 33
View
Gary Cunningham-Lee Minor text edits. 32
View
Marc Laporte 31
View
Marc Laporte fancytable Plugin modified by editor. 30
View
Marc Laporte Staying with same person in a role has some benefits too. Experience, continuity... 29
View
Marc Laporte This should be in the dogfood team 28
View
Marc Laporte fancytable Plugin modified by editor. 27
View
Marc Laporte fancytable Plugin modified by editor. 26
View
Bernard Sfez / Tiki Specialist fancytable Plugin modified by editor. 25
View
Marc Laporte Nelson had removed this section, which makes no sense. The point of a team is to have members who get things done. 24
View
Bernard Sfez / Tiki Specialist 23
View
Bernard Sfez / Tiki Specialist Updating roles for the release team 22
View
Bernard Sfez / Tiki Specialist 21
View
Nelson Ko 20
View
Bernard Sfez / Tiki Specialist 19
View
Bernard Sfez / Tiki Specialist 18
View
Bernard Sfez / Tiki Specialist 17
View
Marc Laporte We want more than one :-) 16
View
Marc Laporte Move to intro page 15
View
Marc Laporte 14
View
  • «
  • 1 (current)
  • 2