Open Stack

On 9/26/2017 7:00 PM, Doug Hellmann wrote:
> Excerpts from Jay S Bryant's message of 2017-09-26 18:39:34 -0500:
>> On 9/26/2017 4:33 PM, Anne Bertucio wrote:
>>
>>> Release marketing is a critical part of sharing what’s new in each release, and we want to rework how the marketing community and projects work together to make the release communications happen.
>>>
>>> Having multiple, repetetive demands to summarize "top features" during release time can be pestering and having to recollect the information each time isn't an effective use of time. Being asked to make polished, "press-friendly" messages out of release notes can feel too far outside of the PTL's focus areas or skills. At the same time, for technical content marketers, attempting to find the key features from release notes, ML posts, specs, Roadmap, etc., means interesting features are sometimes overlooked. Marketing teams don't have the latest on what features landed and with what caveats.
>>>
>>> To address this gap, the Release team and Foundation marketing team propose collecting information as part of the release tagging process. Similar to the existing (unused) "highlights" field for an individual tag, we will collect some text in the deliverable file to provide highlights for the series (about 3 items). That text will then be used to build a landing page on release.openstack.org that shows the "key features" flagged by PTLs that marketing teams should be looking at during release communication times. The page will link to the release notes, so marketers can start there to gather additional information, eliminating repetitive asks of PTLs. The "pre selection" of features means marketers can spend more time diving into release note details and less sifting through them.
>>>
>>> To supplement the written information, the marketing community is also going to work together to consolidate follow up questions and deliver them in "press corps" style (i.e. a single phone call to be asked questions from multiple parties vs. multiple phone calls from individuals).
>>>
>>> We will provide more details about the implementation for the highlights page when that is ready, but want to gather feedback about both aspects of the plan early.
>>>
>>> Thanks for your input,
>>> Anne Bertucio and Sean McGinnis
>>>
>>>
>>>
>>>
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> Anne and Sean,
>>
>> Thank you for starting this effort.  I have been amazed how many times I
>> have been asked for the same information since the end of Pike.  I think
>> that having a more automated process for this would be very helpful.
>>
>> One request would be that the process allow for more than just a 'one
>> liner' on key features.  If this is being targeted at marketing people
>> we will need to be able to provide more information.  So, if we could
>> have something like little commit messages where there is a summary of
>> what the highlight is and then can provide a bit more verbose
>> explanation (a few sentences) I think that would make this addition more
>> helpful.
> I was planning on the usual "embed RST in YAML" pattern. The amount
> of detail you leave will then be completely up to you.
>
> Doug
+2  Sounds like a good plan to me.  Thank you!
>> I look forward to hearing more about this!
>>
>> Jay
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev