Open Stack

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)