Planning juju 0.7 release

[Kapil Thangavelu]

On Tue, Mar 12, 2013 at 7:36 AM, Martin Packman <
martin.packman at canonical.com> wrote:

> I propose cutting a release from pyjuju trunk this Thursday, and also
> releasing new 0.6 and 0.5 minor versions at the same time.
>
>
Sounds good. There's a mechanical issue here though i'd like to delve into
a bit more. There are two release branches in addition to trunk. Currently
trunk is backwards compatible to 0.5.2. Currently most bug fixes have only
been on trunk as well, so would either need to backported (value?) or have
those releases cut from trunk subject to some additional compatibility
testing (client to env).

Also by release is there any intent  to update distro versions / srus on
any of these?



> This would include the recent hook serialisation change, removal of
> the orchestra code, JUJU_ENV_UUID support, and lots of bug fixes. It
> would not include any other exciting, compatibility breaking, changes
> that Kapil might have up his sleeve.
>
>
i've been pretty careful to avoid anything compatibility breaking landing
on trunk, as there are too many users on the trunk ppa for that not to be a
disaster.


> See the milestone pages on launchpad for what's currently landed or
> planned for backporting. I'm aware of a change to the way MAAS file
> storage works that's currently untargetted and may also require
> backporting. Is there anything else that's missing that should be
> included?
>
> <https://launchpad.net/juju/+milestone/0.7>
> <https://launchpad.net/juju/+milestone/0.6.1>
> <https://launchpad.net/juju/+milestone/0.5.3>
>

As i mentioned i'm concerned that some of the bug fixes there might be
improperly labeled as they've only landed trunk.

>
> I plan to remove the 0.7 milestone from any bugs currently targeted
> that are not yet fixed.
>

I've done some bug triage and milestone changes.

thanks,

Kapil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130312/9036533d/attachment-0001.html>