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
On Tue, Jul 14, 2015 at 4:45 PM, Marco Ceppi marco.ce...@canonical.com wrote:
I think you're on the right train of thought as to what this is, but miss a
few important issues this helps address. It's is trivial to copy code
around, and we talk about it all the time in charm schools find a charm
I'm not sure I understand the problems this is solving that aren't
adequately solved by branching from a source charm. It seems like the hard
part of branching - maintaining changes to non-trivial code - is not helped
by this tool. For charms that just need to add hook files or modify charm
Anyone any idea if deploying inside an existing EC2 VPC/Subnet is possible?
I found someone who proposed a patch for this a long time ago but haven't been
able to find anything like this for a more recent version.
https://bugs.launchpad.net/juju/+bug/1073133
Met vriendelijke groet,
Mark
