[OpenStack-docs] Fwd: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Brian Moss kallimachos at gmail.com
Tue Nov 10 05:50:52 UTC 2015


On 10 November 2015 at 06:59, Andreas Jaeger <aj at suse.com> wrote:

> On 11/04/2015 02:27 AM, Christian Berendt wrote:
>
>> On 11/03/2015 09:37 PM, Anne Gentle wrote:
>>
>>> Hi docs peeps, wanted to be sure you see and understand this important
>>> change for releases and release notes.
>>>
>>
>> Who takes care of the reno enablement for the openstack-manuals
>> repository? We should do this prior to opening to the cut of the Liberty
>> branch. This way we do not have to backport the change (step 2).
>>
>> In our next team meeting we should discuss the usage of blueprints on
>> Launchpad.
>>
>
> After digging deeper into this and some discussion with Doug: We recently
> removed all release notes from the guides since we never updated them.
>
> Do we really want to add such notes back to our guides? And if we do, do
> we want guide specific release notes - or do we want release notes for all
> of documentation?
>

I'm in favor of not having documentation release notes for our guides.
Maintenance is a burden and I don't see a great benefit to the reader.
Unless we start getting feedback from users clamoring for documentation rel
notes, I think we should continue with the current approach.

- Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20151110/88219b93/attachment.html>


More information about the OpenStack-docs mailing list