So an interesting thought experiment. What if we made all changes on a
stable series require an associated bug to be able to land the code there.
At least as I understand blocker bugs on a given series, it just requires
that the code proposed for landing be associated with one of the current
list
[as roger.pe...@canonical.com this time]
On 14 July 2015 at 10:02, Nate Finch nate.fi...@canonical.com wrote:
I don't
think it's unreasonable to just make such a bug a blocker, just to get it
addressed ASAP, even if it is not strictly making things worse than an
earlier version.
FWIW I think
I think everyone's agreeing here, but maybe the wording just needs to be
clarified somewhere to avoid confusion.
It sounds like bugs which are assigned to a release do not block commits
unless they are marked blockers. And blockers are determined by we
wouldn't want *anyone* to upgrade to a
On 14/07/15 23:26, Aaron Bentley wrote:
On 2015-07-13 07:43 PM, Ian Booth wrote:
By the definition given
If a bug must be fixed for the next minor release, it is
considered a ‘blocker’ and will prevent all landing on that
branch.
that bug and any other that we say we must include in a
On 14 July 2015 at 15:31, Ian Booth ian.bo...@canonical.com wrote:
On 14/07/15 23:26, Aaron Bentley wrote:
On 2015-07-13 07:43 PM, Ian Booth wrote:
By the definition given
If a bug must be fixed for the next minor release, it is
considered a ‘blocker’ and will prevent all landing on that
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
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:
-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. *
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
