Hello Everyone!
Its time to start thinking about calling out 'cycle-highlights' in your deliverables!
As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Rocky[1], Stein[2], Train[3].
We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start.
*The deadline for cycle highlights is the end of the R-5 week [4] on April 10th.*
How To Reminder: -------------------------
Simply add them to the deliverables/train/$PROJECT.yaml in the openstack/releases repo like this:
cycle-highlights: - Introduced new service to use unused host to mine bitcoin.
The formatting options for this tag are the same as what you are probably used to with Reno release notes.
Also, you can check on the formatting of the output by either running locally:
tox -e docs
And then checking the resulting doc/build/html/train/highlights.html file or the output of the build-openstack-sphinx-docs job under html/train/ highlights.html.
Can't wait to see you all have accomplished this release!
Thanks :)
-Kendall Nelson (diablo_rojo)
[1] https://releases.openstack.org/rocky/highlights.html [2] https://releases.openstack.org/stein/highlights.html [3] https://releases.openstack.org/train/highlights.html [4] htt https://releases.openstack.org/train/schedule.html#t-cycle-highlights https://releases.openstack.org/ussuri/schedule.html