Hi all, I need some consensus on how to handle merge proposals for charms
in the charm charm store when these proposals change configuration key
names. The proposal in question is
https://code.launchpad.net/~sidnei/charms/precise/squid-reverseproxy/trunk/+merge/190500
in
the config.yaml diff the
On 02/11/13 03:32, Kapil Thangavelu wrote:
I'd suggest creating a bug per command (some already have extant bugs),
there's vastly differing amounts of work in them, and its easier to
track progress with appropriately sized tasks. ie kanban style cli api
is a story.
As discussed at the sprint,
Hi folks,
The active reviews page is looking OMG long.
code.launchpad.net/juju-core/+activereviews
Please take some time today to look at the outstanding work that you
have, and work out what can be landed, and chase reviewers for work.
As the author of the work, it is your responsibility to
On 04/11/13 05:11, Tim Penhey wrote:
If the work has been abandoned and is not likely to be landed, mark the
merge proposal as rejected to get it off the list.
It's also good to mark the branch itself as abandoned in that case, so
that it will drop off the default branch listings.
Once you
On Fri, Nov 1, 2013 at 8:31 PM, roger peppe rogpe...@gmail.com wrote:
On 31 October 2013 18:42, Andrew Wilkins andrew.wilk...@canonical.com
wrote:
type State interface {
AllMachines() ([]Machine, error)
}
// another name would be needed, as this clashes with state.Entity; just
