[all][PTL][release] Call for Ussuri Cycle Highlights
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
Hello Everyone! Wanted to bring this to the top of people's inboxes as we are getting close to the deadline! Next week, April 9th (same as Feature Freeze and m3) is the deadline for cycle highlights. If you add them later than that, they might not make it into the release marketing messaging. Can't wait to see what all the projects have accomplished! -Kendall (diablo_rojo) On Wed, Feb 26, 2020 at 12:51 PM Kendall Nelson <kennelson11@gmail.com> wrote:
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
Hi Kendall, we (Kolla) added our cycle highlights already not to miss the deadline but we are cycle-trailing and could be looking for a way to amend if we manage to squeeze more features in (note we are still well before feature freeze). Could you advise whether cycle-trailing projects could amend their cycle highlights later? -yoctozepto pt., 3 kwi 2020 o 22:21 Kendall Nelson <kennelson11@gmail.com> napisał(a):
Hello Everyone!
Wanted to bring this to the top of people's inboxes as we are getting close to the deadline!
Next week, April 9th (same as Feature Freeze and m3) is the deadline for cycle highlights. If you add them later than that, they might not make it into the release marketing messaging.
Can't wait to see what all the projects have accomplished!
-Kendall (diablo_rojo)
On Wed, Feb 26, 2020 at 12:51 PM Kendall Nelson <kennelson11@gmail.com> wrote:
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] htthttps://releases.openstack.org/ussuri/schedule.html
Yes you can definitely add/edit them later! That said, whatever the state is at the deadline is what will be used for marketing for the release. -Kendall (diablo_rojo) On Sat, 4 Apr 2020, 10:53 am Radosław Piliszek, <radoslaw.piliszek@gmail.com> wrote:
Hi Kendall,
we (Kolla) added our cycle highlights already not to miss the deadline but we are cycle-trailing and could be looking for a way to amend if we manage to squeeze more features in (note we are still well before feature freeze).
Could you advise whether cycle-trailing projects could amend their cycle highlights later?
-yoctozepto
pt., 3 kwi 2020 o 22:21 Kendall Nelson <kennelson11@gmail.com> napisał(a):
Hello Everyone!
Wanted to bring this to the top of people's inboxes as we are getting
close to the deadline!
Next week, April 9th (same as Feature Freeze and m3) is the deadline for
cycle highlights. If you add them later than that, they might not make it into the release marketing messaging.
Can't wait to see what all the projects have accomplished!
-Kendall (diablo_rojo)
On Wed, Feb 26, 2020 at 12:51 PM Kendall Nelson <kennelson11@gmail.com>
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
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
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
wrote: 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]. probably used to with Reno release notes. 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] htthttps://releases.openstack.org/ussuri/schedule.html
Noted, thanks! -yoctozepto niedz., 5 kwi 2020 o 06:42 Kendall Nelson <kennelson11@gmail.com> napisał(a):
Yes you can definitely add/edit them later!
That said, whatever the state is at the deadline is what will be used for marketing for the release.
-Kendall (diablo_rojo)
On Sat, 4 Apr 2020, 10:53 am Radosław Piliszek, <radoslaw.piliszek@gmail.com> wrote:
Hi Kendall,
we (Kolla) added our cycle highlights already not to miss the deadline but we are cycle-trailing and could be looking for a way to amend if we manage to squeeze more features in (note we are still well before feature freeze).
Could you advise whether cycle-trailing projects could amend their cycle highlights later?
-yoctozepto
pt., 3 kwi 2020 o 22:21 Kendall Nelson <kennelson11@gmail.com> napisał(a):
Hello Everyone!
Wanted to bring this to the top of people's inboxes as we are getting close to the deadline!
Next week, April 9th (same as Feature Freeze and m3) is the deadline for cycle highlights. If you add them later than that, they might not make it into the release marketing messaging.
Can't wait to see what all the projects have accomplished!
-Kendall (diablo_rojo)
On Wed, Feb 26, 2020 at 12:51 PM Kendall Nelson <kennelson11@gmail.com> wrote:
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] htthttps://releases.openstack.org/ussuri/schedule.html
Last reminder!! Cycle highlights are due tomorrow. You are welcome to add them at a later date, but anything added after tomorrow might not be included in the marketing for the Ussuri release. Thanks! -Kendall (diablo_rojo) On Sun, Apr 5, 2020 at 1:08 PM Radosław Piliszek < radoslaw.piliszek@gmail.com> wrote:
Noted, thanks!
-yoctozepto
niedz., 5 kwi 2020 o 06:42 Kendall Nelson <kennelson11@gmail.com> napisał(a):
Yes you can definitely add/edit them later!
That said, whatever the state is at the deadline is what will be used
for marketing for the release.
-Kendall (diablo_rojo)
On Sat, 4 Apr 2020, 10:53 am Radosław Piliszek, <
Hi Kendall,
we (Kolla) added our cycle highlights already not to miss the deadline but we are cycle-trailing and could be looking for a way to amend if we manage to squeeze more features in (note we are still well before feature freeze).
Could you advise whether cycle-trailing projects could amend their cycle highlights later?
-yoctozepto
pt., 3 kwi 2020 o 22:21 Kendall Nelson <kennelson11@gmail.com>
napisał(a):
Hello Everyone!
Wanted to bring this to the top of people's inboxes as we are getting
close to the deadline!
Next week, April 9th (same as Feature Freeze and m3) is the deadline
for cycle highlights. If you add them later than that, they might not make it into the release marketing messaging.
Can't wait to see what all the projects have accomplished!
-Kendall (diablo_rojo)
On Wed, Feb 26, 2020 at 12:51 PM Kendall Nelson <
kennelson11@gmail.com> wrote:
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
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
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
radoslaw.piliszek@gmail.com> wrote: 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]. probably used to with Reno release notes. 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] htthttps://releases.openstack.org/ussuri/schedule.html
participants (2)
-
Kendall Nelson
-
Radosław Piliszek