This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

We aim to release monthly releases on a time-driven release cycle based on the following phases to plan and manage each release. Soon we'll have a scrum boards up on JIRA to track the stories in each release and manage the backlog for future releases. 



Proposed Length

Planning of Next Release

Discuss with community the features that are ready to be integrate and we would like to ship in the next release. Management of the backlog to plan out what features and tasks are available to work on will be coordinated separately.


  • Create fix version on JIRA to assign to.
  • Modify existing email template to open up planning process
  • Regularly schedule a meeting to discuss and set a tentative branching date (i.e. 2 weeks later, if release date is a month past that).


1 - 2 weeks

Announcement of Release

Announce what is going to come in the release (should be 80% done at least).


  • Cut a release branch and freeze release branch and then develop branch can still have active work on it but only in rare cases might anything additional from develop
  • Email out sharing release branch details


QA begins on the release branch

  • Set up staging server


1 - 2 weeks

JIRA Sanitization & Publish Release Notes

Sanitize release documentation


  • Create release notes and email community release information with links.


Publicly vote for release amongst community with binding votes from committers


  • Create artifacts
  • Sign release, etc.
  • Open up vote via dev list


Tally up votes, announce, update websites and infrastructure with new release artifacts.




  • No labels