• Set a general timeline for each release, according to our Version Lifecycle.
• Pick a star name (Ask community to help here).
• Decide When to branch and create the branch.
• Coordinate with the Wishlist Triage Team to track list of regressions and follow-up to get resolved (triage, blockers management, etc.).
  • Tiki30
• 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 Tiki30.
  • 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).
• Coordinate the actual various release runs (Alpha, Beta, RC) with the Packaging Team.
• Decide when to release.

As with any role, it's important to have more than one person with the skills.

• How to improve the release process

Be in touch with the developments on your release. It's mandatory to be subscribed to the https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel for this, so you can catch up after you're away.

Be available on IRC throughout the release cycle for assistance/support and coordination.

Have knowledge of or background in software engineering.

Be comfortable working with people. Self-sufficient release managers can end up working in isolation. Social skills are a plus, adequate English is useful, too.

Have a Linux computer so you can use the release scripts, and create the tar.gz files. See: How to release.

It's useful to be able to code in PHP, too, especially to fix any last minute showstoppers.

• Rodriguez Nyiringabo
• bienvenu ushindi

• Next Release

• http://en.wikipedia.org/wiki/Release_management

• ReleaseManagerRequirements
• Release Manager
• Release Managers
• Release Coordinator
• Release Coordinators
• Contributions of each Team to the release process