Hello Everyone!
As you may or may not have read last week in the release update from Sean,
its time to call 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
Rocky[1] or this one for Stein[2].
We don't need a fully fledged marketing message, just a few highlights (3-4
ideally), from each project team.
*The deadline for cycle highlights is the end of the R-5 week [3] on Sept
13th.*
How To Reminder:
-------------------------
Simply add them to the deliverables/train/$PROJECT.yaml in the
openstack/releases repo similar to 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.
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/schedule.html
<https://releases.openstack.org/train/schedule.html#t-cycle-highlights>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190905/2cd5dc75/attachment-0001.html>