PPA for "0.6" release of Juju?

[Mark Mims]

+1

On Mon, Sep 17, 2012 at 03:42:38PM -0700, Clint Byrum wrote:
> Hi all. Up until now, we've relied on a single PPA for juju to use when
> juju-origin: ppa is used.
> 
> However, at this point we are starting to see some production usage of
> juju, and this becomes a huge problem for development, unless PPA is
> treated as an experiment only. I think its hard to tell, as a user,
> that the PPA option could potentially break everything though, so it
> would be better if we took steps to make it stable and useful.
> 
> I'd like to propose that we create a new PPA for each release of python
> juju. We've already created the 0.5 PPA, which will be used with the
> upcoming 0.5.2 release so that 0.5.x users don't get all of the new
> changes pulled into trunk. It strikes me that 0.6 should be treated the
> same way, and only get "released" versions of 0.6 when using the PPA.
> 
> The way I propose to do this is to change the PPA in-use to a 0.6 PPA in a
> new 0.6 series branch that will at first track trunk until release day and
> then only receive commits that are part of a 0.6.x series release. Trunk
> will continue to point to ppa:juju/pkgs which will of course be built
> from tip.
> 
> This would also mean that we repeat this whenever a minor version bump
> is made (such as 0.7).
> 
> https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1048770
> 
> -- 
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
> 

-- 
Mark Mims, Ph.D.
Ubuntu Server Team
Canonical Ltd.
mark.mims at canonical.com
+1(512)981-6467