Re: Blocking bugs process

2015-07-13 Thread Nate Finch
Can you put this in the wiki? On Thu, Jul 9, 2015 at 6:33 PM Martin Packman martin.pack...@canonical.com wrote: The QA team have been trying to hammer out a clearer process over blocking bugs, and have put together the document below for discussion. We'll be handling bugs as described here

Re: Blocking bugs process

2015-07-13 Thread Martin Packman
On 13/07/2015, Nate Finch nate.fi...@canonical.com wrote: Can you put this in the wiki? Done, with Aaron's addition: https://github.com/juju/juju/wiki/Blocking-bugs -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at:

Re: Blocking bugs process

2015-07-13 Thread Aaron Bentley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-07-09 06:33 PM, Martin Packman wrote: == Unblocking == * All bugs tagged ci blocker will be marked fix-released when the branch has a blessed tip. * QA will mark all other blockers fix-released when they determine them to be fixed. *

Re: Blocking bugs process

2015-07-13 Thread Martin Packman
Thank you for responding Ian. On 13/07/2015, Ian Booth ian.bo...@canonical.com wrote: == Definition of blocking bugs == Master and all release branches should always be in a releasable state. If a bug must be fixed for the next minor release, it is considered a ‘blocker’ and will prevent all