[openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags
jpichon at redhat.com
Tue Aug 9 11:12:00 UTC 2016
Thank you for the replies on this thread and apologies for the delay, I
didn't quite grasp what "this should be a policy" actually meant :-)
On 18 July 2016 at 17:23, Ben Nemec <openstack at nemebean.com> wrote:
> On 07/18/2016 06:28 AM, Julie Pichon wrote:
>> On Friday Dougal mentioned on IRC that he hadn't realised there was a
>> separate project for tripleo-common bugs on Launchpad  and that he'd
>> been using the TripleO main tracker  instead.
>> Since the TripleO tracker is also used for client bugs (as far as I can
>> tell?), and there doesn't seem to be a huge amount of tripleo-common
>> bugs perhaps it would make sense to also track those in the main
>> tracker? If there is a previous conversation or document about bug
>> triaging beyond  I apologise for missing it (and would love a
>> URL!). At the moment it's a bit confusing.
> +1. Given the heavily interconnected nature of tripleo-common,
> tripleoclient, t-h-t, puppet-triple, et al I think it would get a bit
> crazy trying to track bugs with repo-specific trackers.
> Rather than use the wiki, whose future is in doubt, I would like to
> propose that this become a policy like
Thank you for the link. I made a first attempt at a policy over
there  based on this thread and taking some inspiration from the
Neutron folks . The initial list is based on existing TripleO tags,
tags that came up in this conversation and the wider OpenStack project
tags. Let me know what you think!
>> If we do encourage using the same bug tracker for multiple components,
>> I think it would be useful to curate a list of official tags . The
>> main advantage of doing that is that the tags will auto-complete so
>> it'd be easier to keep them consistent (and thus actually useful).
>> Personally, I wanted to look through open bugs against
>> python-tripleoclient but people use different ways of marking them at
>> the moment - e.g. [tripleoclient] or [python-tripleoclient] or
>> tripleoclient (or nothing?) in the bug name. I tried my luck at adding
>> a 'tripleoclient' tag  to the obvious ones as an example. Maybe
>> something shorter like 'cli', 'common' would make more sense. If there
>> are other tags that come back regularly it'd probably be helpful to
>> list them explicitly as well.
>>  https://bugs.launchpad.net/tripleo-common
>>  https://bugs.launchpad.net/tripleo
>>  https://wiki.openstack.org/wiki/TripleO#Bug_Triage
>>  https://wiki.openstack.org/wiki/Bug_Tags
>>  https://bugs.launchpad.net/tripleo?field.tag=tripleoclient
More information about the OpenStack-dev