| 1 |
.. _plan-next-release-content: |
| 2 |
|
| 3 |
Plan next release content |
| 4 |
========================= |
| 5 |
|
| 6 |
1. Ensure a milestone ``X.Y.Z`` exists for the upcoming release. |
| 7 |
|
| 8 |
2. Create an issue for each feature request. |
| 9 |
|
| 10 |
3. During a :ref:`Technical Steering Committee (TSC) meeting |
| 11 |
<organize-tsc-meeting>`, present the proposed list of feature requests for |
| 12 |
the next release. |
| 13 |
|
| 14 |
* Discuss the proposal with the TSC and meeting participants. |
| 15 |
* The TSC validates and finalizes the feature list for the upcoming version. |
| 16 |
|
| 17 |
4. Assign the release milestone to all selected feature issues. |
| 18 |
|
| 19 |
5. Once the initial feature scope is defined, estimate a target due date |
| 20 |
(with quarter-level precision). |
| 21 |
|
| 22 |
* Set the estimated due date in the GitHub milestone properties. |
| 23 |
|
| 24 |
6. Review the feature list at every TSC meeting. |
| 25 |
|
| 26 |
* Depending on project status and scheduling constraints, the TSC may |
| 27 |
add or remove items from the release scope. |
| 28 |
|
| 29 |
7. Maintainers should prioritize relevant external contributions that can |
| 30 |
be included in the upcoming release. |
| 31 |
|
| 32 |
.. vim:set tabstop=2 shiftwidth=2 expandtab autoindent: |