On 28/05/14 21:54, Curtis Hovey-Canonical wrote:
I don't think we can do a release this week, or if we do, the release will be from a version that works from last week.The current blocker is lp:juju-core r2803 or lp:juju-core r2804 broke local precise deployments. Juju cannot bootstrap. https://bugs.launchpad.net/juju-core/+bug/1324255 CI has stumbled from one regression to the next this week. Each fix is followed by another feature that breaks CI. Since we intend to switch to github in a matter of hours, CI has little time to bless a recent revision for release. As I have been doing analysis of the problems, I have not had time to update CI to build tarballs from git. I will now work on that since I don't believe there is anything I can do to convince CI that juju trunk is releasable.
It's highly likely that this is caused by the change to have local provider use replica sets. I'll setup a precise VM and see if I can confirm. If so we should back out that change. *sigh* (and sorry if it is indeed the case).
Michael
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
