With the RT, the tools code in juju has been made to work without the official repository being available, so strictly speaking it is not a blocker. However, under the covers the effect is that juju has a bunch of legacy code and the tools fetching process is complicated. Once the repository is available, it still needs to be populated and the tools code in juju cleaned up. My opinion is that we could release 1.15 and ensure everything is sorted for 1.16.
On 25/09/13 07:47, Curtis Hovey-Canonical wrote: > Gentlemen. > > We have an aggressive release schedule to deliverer 1.16.0 for saucy. > I think we need to release 1.15.0 this week and 1.16.0 next week. > I think we are blocked by RT #63925: Repository for downloading Juju > tool tarball > https://rt.admin.canonical.com//Ticket/Display.html?id=63925 > I also see a unworked number of bugs targeted to 1.15.0 > https://launchpad.net/juju-core/+milestone/1.15.0 > I see 3 bugs targeted to 1.16.0 that are about a great 30 minute experience. > https://launchpad.net/juju-core/+milestone/1.16.0 > > What say you? Are we blocked by the RT? If RT is resolved, do we > release? Do we want to defer the unworked bugs? Would we commit to > resolving some of these for 1.16.0? > > PS The 1.15.0 release notes are at > https://docs.google.com/a/canonical.com/document/d/1o8YsLrQuadB1gbd5veJ3cpN_r2uozKwwTmIh1RmOVHM/edit# > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
