Mature Release Process

Introduction

This section is an attempt to provide convenient material in support of the Technical Community Charter (TCC) section 3.4 Mature Release process.

A Project’s Committers make all decisions about Releases of that Project. However, to be eligible to be considered ‘Mature’, and project must demonstrate a history of following the Mature Release Process. The purpose of the Mature Release Process is to insure openness and maximum opportunity for participation. The idea is to have a simple, clear, public declaration of what a project intends to do and when, and what was actually done in a release cycle. Towards that end, a project following the ‘Mature Release Process’ should have a Release Plan published at the beginning of its release cycle by its committers, and a Release Review just prior to the project release. Both Release Plan and Release Review documents are intended to be relatively short, simple, and posted publicly on the wiki to assist project in coordinating amount themselves and the general world in gaining visibility.

Release Plans

Recommendations on Placement of Release Plans

It is recommended that projects create their Release Plan in the wiki in a uniform way at ${url of project page}/Release_Plans/Release_Plan_${release version}. Example: If a projects page is at https://wiki.fd.io/view/Projects/Foo and it is doing release planning for release 1.1.0, then its release plan would then be:

https://wiki.fd.io/view/Projects/Foo/Release_Plans/Release_Plan_1.1.0

Recommendations on Placement of Release Reviews

It is recommended that projects create their Release Review in the wiki in a uniform way at ${url of project page}/Release_Reviewss/Release_Review_${release version}. Example: If a projects page is at https://wiki.fd.io/view/Projects/Foo and it is doing release planning for release 1.1.0, then its release plan would then be:

https://wiki.fd.io/view/Projects/Foo/Release_Reviews/Release_Reviews_1.1.0