Re: [openstack-dev] [release][PTL] Cycle highlights reminder

[Anne Bertucio]

Hi all,

With Queens-3 behind us and RC1 coming up, wanted to give a gentle reminder 
about the cycle-highlights. To get the party started, I added an example 
highlight for Cinder, Horizon, Ironic and Nova (modify as necessary!): 
https://review.openstack.org/#/c/540171/ 


Hopefully this is a fairly painless process that comes with the great reward of 
not answering “What changed in this release?” five times over to various 
marketing and press arms. I’m definitely looking to refine how we handle 
release communications, so come find me in Dublin with all your feedback and 
suggestions!

Cheers,
Anne Bertucio
OpenStack Foundation
a...@openstack.org | 206-992-7961




> On Dec 22, 2017, at 1:06 AM, Thierry Carrez  wrote:
> 
> Matt Riedemann wrote:
>> On 12/14/2017 2:24 PM, Sean McGinnis wrote:
>>> Hey all,
>>> 
>>> As we get closer to Queens-3 and our final RCs, I wanted to remind
>>> everyone
>>> about the new 'cycle-highlights' we have added to our deliverable info.
>>> 
>>> Background
>>> --
>>> 
>>> As a reminder on the background, we were finding that a lot of PTLs were
>>> getting pings several times at the end of every release cycle by
>>> various folks
>>> asking for highlights of what was new and what significant changes
>>> were coming
>>> in the new release. It was often the same answer to journalists, product
>>> managers, and others that needed to compile that info.
>>> 
>>> To try to mitigate that somewhat, we've built in the ability to
>>> capture these
>>> highlights as part of the release. It get compiled and published to
>>> the web
>>> site so we have one place to point these folks to. It is intended as a
>>> place
>>> where they can get the basic info they need, not as a complete marketing
>>> message.
>>> 
>>> As you prepare for upcoming releases, please start to consider what
>>> you might
>>> want to show up in this collection. We ideally want just a few
>>> highlights,
>>> probably no more than 3 or 4 in most cases, from each project team.
>>> [...]
> 
>> I didn't see this before the q1 or q2 tags - can the cycle highlights be
>> applied retroactively?
> 
> Cycle highlights are a once-at-the-end-of-the-cycle thing, not a
> per-milestone or per-intermediary-release thing. So you don't need to
> apply anything retroactively for the q1 or q2 milestones.
> 
> Basically near the end of the cycle, you look back at what got done in
> the past 6 months and extract a few key messaging points. Then we build
> a page with all the answers and point all marketing people to it --
> which should avoid duplication of effort in answering a dozen separate
> information requests.
> 
> -- 
> Thierry Carrez (ttx)
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org 
> ?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release][PTL] Cycle highlights reminder

[Thierry Carrez]

Matt Riedemann wrote:
> On 12/14/2017 2:24 PM, Sean McGinnis wrote:
>> Hey all,
>>
>> As we get closer to Queens-3 and our final RCs, I wanted to remind
>> everyone
>> about the new 'cycle-highlights' we have added to our deliverable info.
>>
>> Background
>> --
>>
>> As a reminder on the background, we were finding that a lot of PTLs were
>> getting pings several times at the end of every release cycle by
>> various folks
>> asking for highlights of what was new and what significant changes
>> were coming
>> in the new release. It was often the same answer to journalists, product
>> managers, and others that needed to compile that info.
>>
>> To try to mitigate that somewhat, we've built in the ability to
>> capture these
>> highlights as part of the release. It get compiled and published to
>> the web
>> site so we have one place to point these folks to. It is intended as a
>> place
>> where they can get the basic info they need, not as a complete marketing
>> message.
>>
>> As you prepare for upcoming releases, please start to consider what
>> you might
>> want to show up in this collection. We ideally want just a few
>> highlights,
>> probably no more than 3 or 4 in most cases, from each project team.
>> [...]

> I didn't see this before the q1 or q2 tags - can the cycle highlights be
> applied retroactively?

Cycle highlights are a once-at-the-end-of-the-cycle thing, not a
per-milestone or per-intermediary-release thing. So you don't need to
apply anything retroactively for the q1 or q2 milestones.

Basically near the end of the cycle, you look back at what got done in
the past 6 months and extract a few key messaging points. Then we build
a page with all the answers and point all marketing people to it --
which should avoid duplication of effort in answering a dozen separate
information requests.

-- 
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release][PTL] Cycle highlights reminder

[Matt Riedemann]

On 12/14/2017 2:24 PM, Sean McGinnis wrote:

Hey all,

As we get closer to Queens-3 and our final RCs, I wanted to remind everyone
about the new 'cycle-highlights' we have added to our deliverable info.

Background
--

As a reminder on the background, we were finding that a lot of PTLs were
getting pings several times at the end of every release cycle by various folks
asking for highlights of what was new and what significant changes were coming
in the new release. It was often the same answer to journalists, product
managers, and others that needed to compile that info.

To try to mitigate that somewhat, we've built in the ability to capture these
highlights as part of the release. It get compiled and published to the web
site so we have one place to point these folks to. It is intended as a place
where they can get the basic info they need, not as a complete marketing
message.

As you prepare for upcoming releases, please start to consider what you might
want to show up in this collection. We ideally want just a few highlights,
probably no more than 3 or 4 in most cases, from each project team.

Usage
-

This is done by adding some information to deliverables/queens/$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.

You can check on the formatting of the output by either running locally:

tox -e docs

And checking the resulting file under doc/build/html/queens/highlights.html, or
you can view the output of the build-openstack-sphinx-docs job under
html/queens/highlights.html.

Ongoing
---

We now have three different places that document activities for three different
audiences:

Commit messages:  Developer documentation
Release notes:End user and deployer documentation
Cycle highlights: Journalists, product manager, and others

This will be the first release cycle with this last data source. It is our hope
that this will ease some of the burden for this information from the PTLs. If
you still get requests, please try to direct them here to spread awareness.

Thanks!

--
Sean McGinnis (smcginnis)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



I didn't see this before the q1 or q2 tags - can the cycle highlights be 
applied retroactively?


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [release][PTL] Cycle highlights reminder

[Sean McGinnis]

Hey all,

As we get closer to Queens-3 and our final RCs, I wanted to remind everyone
about the new 'cycle-highlights' we have added to our deliverable info.

Background
--

As a reminder on the background, we were finding that a lot of PTLs were
getting pings several times at the end of every release cycle by various folks
asking for highlights of what was new and what significant changes were coming
in the new release. It was often the same answer to journalists, product
managers, and others that needed to compile that info.

To try to mitigate that somewhat, we've built in the ability to capture these
highlights as part of the release. It get compiled and published to the web
site so we have one place to point these folks to. It is intended as a place
where they can get the basic info they need, not as a complete marketing
message.

As you prepare for upcoming releases, please start to consider what you might
want to show up in this collection. We ideally want just a few highlights,
probably no more than 3 or 4 in most cases, from each project team.

Usage
-

This is done by adding some information to deliverables/queens/$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.

You can check on the formatting of the output by either running locally:

   tox -e docs

And checking the resulting file under doc/build/html/queens/highlights.html, or
you can view the output of the build-openstack-sphinx-docs job under
html/queens/highlights.html.

Ongoing
---

We now have three different places that document activities for three different
audiences:

Commit messages:  Developer documentation
Release notes:End user and deployer documentation
Cycle highlights: Journalists, product manager, and others

This will be the first release cycle with this last data source. It is our hope
that this will ease some of the burden for this information from the PTLs. If
you still get requests, please try to direct them here to spread awareness.

Thanks!

--
Sean McGinnis (smcginnis)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev