...
In order to participate in the simultaneous release, a project must exist (see the list of existing projects or create a new project proposal) and do the following things.
...
- Projects must declare their intent to participate in the Simultaneous Release by M0. This is accomplished by:
- providing the Increment blueprint
- adding the project to the Release Scope Table
- sending the first milestone readout mail to TSC email list
- .
- Participating, approved by TSC projects, must publish a candidate Release Plan shortly after M0, and declare their final Release Plan by M1 - the Increment blueprint and the Release Scope Table must must be updated accordingly
- Projects are required to negotiate cross-project dependencies for any new or modified APIs.
- Projects are encouraged to think about any cross-project incompatibilities and how to resolve them, if possible, as part of their release plans.
- Participating project Release Plans must contain Milestones that minimally line up with the Simultaneous Release Plan Milestones
- Release plans should contain a complete list of the exposed APIs including the defined properties defined above, e.g., the name of the interface, a short name, and the list of supporting bundles.
- Per-project release plans now include sections for cross-project negotiation of provided APIs and for noting cross-project incompatibilities.
- All projects participating in the release are also required to participate in the stability releases described in the schedule after the formal release.
...
- Project Team Leader must be elected and confirmed as described in the TSC charter. Casey Cain will help projects with this process and it must be completed by M0.
- The results of the election, and other changes to the project lead during this release, should be reported by
- Updating the project facts for the project on its main wiki page
- Updating the Release Scope Table of this release
- Sending an e-mail to the TSC email list
...