Open Stack

On 1/30/17, 9:21 AM, "Joseph Robinson" <joseph.robinson at RACKSPACE.COM>
wrote:

>Hi all,
>
>
>Following our new PTL Alex’s summary of the bug triager plan (congrats
>again, and also kudos to Lana), I have an example bug triage schedule.
>
>
>A possible plan is to follow the release milestones. And then break down
>those milestones further to reduce burnout (dates are not official):
>
>
> Feb 24 - Pike PTG
>Bug Triager #1 Feb 24 – Mar 3
>
>
>Bug Triager #2 Mar 3 – Mar 10
>March 10 - Pike Milestone 1
>Bug Triager #3 Mar 10 – Mar 24
>
>
>Bug Triager #4 Mar 24 – April 5
>April 5 Pike Milestone 2
>Bug Triager #5 April 5 – April 19
>
>
>Bug Triager #6 April 19 – May 3
>May 18 Pike Milestone 3
>Bug Triager #7 May 3 – May 18
>
>
>Bug Triager #8 May 18 – June 1
>June 14 Pike Release
>Bug Triager #9 June 1 – June 18
>
>

Most of the triage blocks above seem to be roughly two weeks, so how about
making the role rotate every two weeks, coinciding with the Doc Team IRC
meeting? That way we can have a section of the meeting where the outgoing
triager can provide a brief summary of bug activity for the previous two
weeks, while the new triager is identified and handed over to for the
coming two weeks.

Sticking to a regular length of time rather than trying to tie it to
release milestones should make it easier to manage.

Thanks!

John


________________________________
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.