[OpenStack-docs] FW: [openstack-doc-core] Bug triaging
Joseph Robinson
joseph.robinson at RACKSPACE.COM
Mon Jan 30 09:03:43 UTC 2017
Hi all, replies in line - I have a separate email with the plan, which I
am about to send.
On 27/01/2017, 10:43 PM, "John Davidge" <John.Davidge at rackspace.com> wrote:
>On 1/27/17, 12:25 PM, "Alexandra Settle" <a.settle at outlook.com> wrote:
>
>>Hi manuals team,
>>
>>As some of you may or may not have noticed, I¹ve spent the last 2 weeks
>>living in Launchpad Land triaging our, rather large, set of bugs.
>
>Thank you for doing this, I¹ve been seeing the number of bugs tumbling
>down and it¹s very satisfying to watch.
>
>>I'd like there to be designated bug triager for all 'new' bugs.
>
>We¹ve had a rotating bug triage role (Bug Deputy[1]) in the neutron team
>for a long time now and it is AWESOME. Definitely something I¹d love to
>see come to Docs.
That¹s great news, good to hear another project team has tried a similar
plan.
>
>>There are approximately 1-3 bugs max that come into the manuals per-day.
>>It's not a heavy job, but it's
>> something we have to start doing regularly to lighten the load and
>>ensure we¹re catching the right issues at the right time. Joseph
>>suggested we could rotate the responsibility, and Andreas suggested that
>>each core takes on this responsibility
>> which I completely agree with.
>
>As well as cores, it would be great to encourage non-core contributors to
>take on the role, as it¹s a great way to quickly familiarize yourself with
>the various parts of the project and gain confidence in contributing.
>
>>
>>Using the appropriate guide tags, the specialty teams would then in
>>charge of ensuring their bug lists are looked after. The rotation would
>>be aligned with the release cycles (another suggestion from Joseph,
>> thank you!).
>
>When you mention aligning the rotation with release cycles, do you mean
>only one Bug Deputy per cycle? Rotating more regularly can help to prevent
>burn out and give more people the opportunity to participate. In neutron
>we rotate every week[2].
The ³Bug Deputy² idea, added to the meeting as a discussion topic, is a
great idea too.
>
>>
>>Other projects take on similar ways to triage their bug list, and I think
>>it would be a valuable move in the future for all of us to take on this
>>responsibility. Thoughts, concerns, feelings, questions?
>>
>>Thanks,
>>
>>Alex
>>
>
>Great idea, sign me up for a shift!
>
>John
>
>[1]
>http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug
>-
>deputy
>[2] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy
>
>________________________________
>Rackspace Limited is a company registered in England & Wales (company
>registered number 03897010) whose registered office is at 5 Millington
>Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy
>policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This
>e-mail message may contain confidential or privileged information
>intended for the recipient. Any dissemination, distribution or copying of
>the enclosed material is prohibited. If you receive this transmission in
>error, please notify us immediately by e-mail at abuse at rackspace.com and
>delete the original message. Your cooperation is appreciated.
>_______________________________________________
>OpenStack-docs mailing list
>OpenStack-docs at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
________________________________
Rackspace Hosting Australia PTY LTD a company registered in the state of Victoria, Australia (company registered number ACN 153 275 524) whose registered office is at Level 1, 37 Pitt Street, Sydney, NSW 2000, Australia. Rackspace Hosting Australia PTY LTD privacy policy can be viewed at www.rackspace.com.au/company/legal-privacy-statement.php - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com and delete the original message. Your cooperation is appreciated.
More information about the OpenStack-docs
mailing list