Planning juju 0.7 release

[Martin Packman]

On 12/03/2013, Kapil Thangavelu <kapil.thangavelu at canonical.com> wrote:
> 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?

Yes, though the SRU process takes a while so won't all get done on
Thursday. I'd like 0.7 in raring at least for testing of the distro
package.

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

Right, some of them have yet to be backported - generally those not
marked fixed for the series, but perhaps some marked fixed too. I'll
check and backport these before doing the release.

The question is whether there are bugs fixed on trunk that either
don't have a 0.5.3/0.6.1 milestone set, or don't have a launchpad bug
entry at all, that do in fact need to land there?

> I've done some bug triage and milestone changes.

Thanks!

Martin