Move Cycle Highlights task to R-4

Cycle Highligts original deadline was the same as Feature Freeze date.
This caused extra burden to PTLs as while they were reviewing the last
patches at FF, they also needed to write the highligts at the same
time.

This patch postpones one week the Cycle Highlights task so that the
deadline indicates more that is needed AFTER the projects feature
freeze, but still gives the time to Marketing team to process the
cycle highligts.

Note that the best is to collect the Cycle Highlights in advance as
much and as soon as possible, because for Marketing team perspective
having an incomplete list of highlights is better than waiting until a
complete list can be constructed.

Change-Id: Ibe8f0faebcce480bac79a789fb689112038b48c8
This commit is contained in:
Előd Illés 2022-09-02 17:49:24 +02:00
parent fe6c6be845
commit d3823d0d6d
3 changed files with 8 additions and 7 deletions
doc/source

@ -178,8 +178,8 @@ The Antelope coordinated release will happen on Wednesday, 22 March, 2023.
Cycle Highlights
----------------
Cycle highlights need to be added to the release deliverables by feature
freeze to be included in any marketing release messaging.
Cycle highlights need to be added to the release deliverables after the
feature freeze to be included in any marketing release messaging.
Highlights may be added after this point, but they will likely only be
useful for historical purposes.

@ -82,10 +82,11 @@ cycle:
- a-final-clientlib
- a-soft-sf
- a-rf
- a-cycle-highlights
- end: '2023-02-24'
name: R-4
start: '2023-02-20'
x-project:
- a-cycle-highlights
- end: '2023-03-03'
name: R-3
start: '2023-02-27'

@ -869,10 +869,6 @@ R-5 week (Milestone-3)
#. Process any remaining library freeze exception.
#. Early in the week, email openstack-discuss list to remind PTLs that
cycle-highlights are due this week so that they can be included in
release marketing preparations.
#. Propose autoreleases (``process_auto_releases``) for
``cycle-with-intermediary`` client libraries which had commits that have
not been included in a release.
@ -1017,6 +1013,10 @@ R-4 week
#. Process any remaining client library freeze exception.
#. Early in the week, email openstack-discuss list to remind PTLs that
cycle-highlights are due this week so that they can be included in
release marketing preparations.
#. Freeze all cycle-based library releases except for release-critical
bugs. Independently-released libraries may still be released, but
constraint or requirement changes will be held until after the freeze