What is happening with the 1.11.2 (nee 1.11.1) release

[David Cheney]

Hello,

Here is a short status update on the 1.11.2 release.

The release was originally scheduled for the friday, there was a delay
while a final bug fix was committed, as the 1.11.1 tag was cut by then, the
release version has been bumped to 1.11.2. Sorry for the confusion.

The next attempt at the release was made this Monday. The code built fine
and was pushed in to the juju/devel PPA, and tools tarballs were pushed up
to s3 however during the release validation afterwards this release was not
able to bootstrap any ec2 environments (status of other environments
unknown; not attempted).

Building locally from the same source failed to reproduce the problem.
Searching the archive this issue has happened before,
https://lists.ubuntu.com/archives/juju-dev/2013-April/000913.html, but we
failed to investigate at the time.

During diagnosis of this problem a new issue was discovered[1]; juju-core
cannot build on Precise builders due to a bug in the version of Go that
ships with P.

What is more confusing is on Monday a successful build of 1.11.2 was made
from a builder that claims to be running Precise. Trying to replicate this
on a Precise machine showed that 1.11.2 could _not_ be built on Precise.

So, we have at least two problems. Both are related to what the builders
have installed on them and the way it affects the final bits that lands the
juju/devel PPA.

Dave

[1] https://bugs.launchpad.net/juju-core/+bug/1196811
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130702/79ed26f4/attachment.html>