Re: [openstack-dev] [OpenStack-docs] [stable] New config options, no default change
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
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-docs] [stable] New config options, no default change
On Tue, Dec 2, 2014 at 5:10 PM, 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? > Yep, there sure is. https://wiki.openstack.org/wiki/GitCommitMessages#Including_external_references > > For now I've been simply collecting stable releasenote-worthy changes > manually in etherpad https://etherpad.openstack.org/p/StableJuno > > > Cheers, > Alan > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-docs] [stable] New config options, no default change
>> 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? For now I've been simply collecting stable releasenote-worthy changes manually in etherpad https://etherpad.openstack.org/p/StableJuno Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-docs] [stable] New config options, no default change
On Tue, Dec 2, 2014 at 3:44 PM, Steve Gordon wrote: > - Original Message - > > From: "Anne Gentle" > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > > > On Tue, Dec 2, 2014 at 2:59 PM, Alan Pevec wrote: > > > > > > Will the bugs created by this end up in the openstack-manuals project > > > (which I don't think is the right place for them in this case) or has > it > > > been set up to create them somewhere else (or not at all) when the > commits > > > are against the stable branches? > > > > > > Docs team, how do you handle DocImpact on stable/branches, do you mind > > > (mis)using your tag like this? > > > I thought DocImpat only triggers a notification for the docs team, if > > > there's more machinery behind it like automatic bug filing then we > > > should use a different tag as stable relnotes marker. > > > > > > > We have recently enabled DocImpact tracking for more projects. DocImpact > > currently creates a bug in the project indicated by the project's build > > config in openstack-infra/project-config/gerrit/projects.yaml setting > > docimpact-group:, such as: > > docimpact-group: oslo > > > > If you want to track your DocImpact feel free to use a Launchpad project > > for docimpact-group that makes sense to you. > > Anne > > 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? Anne > > -Steve > > ___ > OpenStack-docs mailing list > openstack-d...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
