On 12/03/2014 12:10 AM, Alan Pevec wrote: >>> In this case we're referring to how we handle DocImpact for specific >>> branches of a project (say stable/juno of Nova, for example). I don't think >>> we'd want to change the DocImpact handling for the entire project to go >>> somewhere other than openstack-manuals. As far as I know the current setup >>> doesn't support us changing the handling per branch though, only per >>> project. >> >> >> Yep, I do agree. And honestly we don't have the resources to cover stable >> branches docs in addition to the ongoing. >> >> Is there another way to tag your work so that you remember to put it in >> release notes? > > We just started discussing this and it is not used yet and we'll pick > some other tag. > While at it, is there an OpenStack-wide registry for tags in the > commit messages?
Not sure - but if you do define one, please send a patch for the infra-manual: http://docs.openstack.org/infra/manual/developers.html#peer-review Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
