Open Stack

On 2015-11-10 08:30, Christian Berendt wrote:
> On 11/09/2015 09:59 PM, Andreas Jaeger wrote:
>> 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 think it makes no sense to have guide specific release notes. But I
> think it makes sense to have release notes for openstack-manuals
> repository to be able to write down the overall process (contributor
> guide added, guide xy migrated to RST, ..).

What kind of tracking do we need for this?

Note that we didn't do any release notes at all for Liberty:
https://wiki.openstack.org/wiki/ReleaseNotes/Liberty

For Kilo we did some:
https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Documentation

Looking at those, a single "RELEASENOTES" file might be enough for 
tracking all our guides - instead of using reno which works under the 
assumption currently that we use tags for release. So, to support 
openstack-manuals, we would first need to enhance it. And we don't have 
that many new features that we get many merge conflicts.

So, my proposal: Let's use reno for the tools like all OpenStack 
projects with proper releases. Let's add for openstack-manuals a single 
file that tracks release notes for all our repos (and thus revert the 
addition of reno to it). For the N cycle we can revisit this again...


Andreas
-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
        HRB 21284 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126