Add note to model changing task

As some deliverables don't really fit the cycle-with-rc model but
released only once per cycle, the process would still suggest the model
change. This patch adds a note that for such cases the model change
is not a must.

Change-Id: I3ae583dab2df800a40fbca449fd2e6f08425bd5a
This commit is contained in:
Előd Illés 2022-08-17 17:27:10 +02:00 committed by Thierry Carrez
parent 4502c07289
commit 06d65d6001

@ -570,8 +570,18 @@ Between Milestone-2 and Milestone-3
switch to the cycle-with-rc model, which is much more suitable for
deliverables that are only released once per cycle.
Propose a release model change for all deliverables meeting that criteria.
PTLs and release liaisons may decide to:
.. note::
Not every deliverable meeting the above criteria should be encouraged
to change release model. For example if there are very limited changes
per cycle, a single release without RCs is probably OK. A team may
also want to keep the possibility of releasing multiple times per
cycle.
Deliverables possibly meeting the criteria should be reviewed during the
release meeting, and a release model change should be proposed for all
deliverables where it could make sense. PTLs and release liaisons may
decide to:
- immediately release an intermediary release (and -1 the proposed change)
- confirm the release model change (+1 the proposed change)