BuildStream 1.2 Feature freeze communication
Background
The feature freeze is the second major technical action of the BuildStream 1.2 release, after branching. This action needs to be communicated through the mailing list by the release manager in order to officially declare that we get into the following phase of the release process: beta phase.
Task description
The communication of the end of the feature freeze phase, Feature Freeze Declaration, so the beginning of the Beta phase of the release process involves the following actions:
-
Create the communication. -
Review the communication by the Release manager. -
Send the communication through the community mailing list.
Communication description
The communication should include:
-
Statement declaring Feature Freeze. -
Which planned feature (major) will be part of the release and which won't. -
Expectations from the release manager towards the developers during the Beta phase. -
Planned date for the Beta release. - If there is a change compared to the already communicated plan, it has to be highlighted.
- Include a link to the Version release schedule/roadmap (note: we do not have it published yet. You can use the GNOME one).
Considerations for this release
- For this release, the Feature Freeze announcement and the BuildStream 1.2 Beta Release Announcement will be the done in the same communication, through the mailing list.
- BuildStream 1.2 Beta = BuildStream 1.1.5
Relation with other tasks
- This tasks precedes and block #13 (closed)
Acceptance Criteria
Link to the Feature freeze announcement in the ML: https://mail.gnome.org/archives/buildstream-list/2018-August/msg00017.html
Edited by toscalix