Fwd: Freshness of PPAs

[Mark Shuttleworth]

This is why we put a more semantic structure into snap channels. In snap
channels the sequence of fallback (from edge to beta to candidate to
stable) is predictable. We also are gaining proper series for snaps, so
people won't get major version jump unless they want the latest bits
explicitly.

I think we should drop the MAAS PPAs in favour of classic snaps en route
to strictly confined snaps.

Mark

On 22/01/17 01:42, John A Meinel wrote:
> What is the actual release order for packages in the PPAs. I noticed
> that:
>
>   * Yakkety has 2.1.3+bzr5573-0
>   * ~maas/stable has 2.1.2+bzr5555
>   * ~maas/proposed has 2.1.3+bzr5573
>   * ~maas/next has 2.1.0+bzr5480
>   * ~maas/next-proposed has 2.0.0~rc4
>
> I would have thought that things would flow from next-proposed into
> next, into proposed, into stable, into the official archive.
>
> It does look like 'proposed' has the version that ended up in the
> official Archive (at least for Yakkety). Is the intent that after it
> goes into the archive it will end up in 'stable'?
>
> My intent is to have 2 MAAS controllers for testing, one running
> whatever is the current stable, and one running whatever is in
> development so that I can be prepared for any changes that might come up.
>
> I was hoping I could point at either 'next' or 'next-proposed', but
> both of those seem much more out of date than stable and proposed.
>
> Advice welcome,
> John
> =:->
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170122/99ada20f/attachment.html>