Request for new 1.18 release

[Curtis Hovey-Canonical]

On Fri, May 30, 2014 at 12:45 PM, Robie Basak <robie.basak at ubuntu.com> wrote:
> (wrong list address; I'll try again)
>
> Hi Curtis,
>
> The current 1.18 tip fixes bugs relating to Utopic in distribution
> packaging. I need these fixes to fix juju-core on Utopic, and juju-core
> in Utopic is currently blocking updating juju-core in Trusty to the
> latest 1.18 release, which is blocking me from fixing juju-quickstart in
> Trusty.
>
> Please could we have a new 1.18 stable release, based on current 1.18
> tip?
>
> The tree of blockers is quite twisted to try and explain, but I believe
> that a new 1.18 release will unblock everything now.
>
> juju-quickstart problem on Trusty:
> https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1306537
>
> The fixes I need in a release to fix Utopic:
>
> http://bazaar.launchpad.net/~go-bot/juju-core/1.18/revision/2290
> http://bazaar.launchpad.net/~go-bot/juju-core/1.18/revision/2294

CI has blessed  lp:juju-core/1.18 r2295. This is how I found the
tarball that will be released
    http://juju-ci.vapour.ws:8080/
        revision-results job summarises the blessed and cursed revisions
    http://juju-ci.vapour.ws:8080/job/revision-results/
        Blessed: lp:juju-core/1.18 r2295 (Build #1424)
    http://juju-ci.vapour.ws:8080/job/build-revision/
        #1424
        lp:juju-core/1.18 r2295
    http://juju-ci.vapour.ws:8080/job/build-revision/1424/
       There is the tested tarball. It is the one we will release.

There is an additional fix issue being prepared for 1.18 4 may wait for it.

Also, since your goal was to get the tarball of what will be released,
I have just revealed how I find the tarball that will be released. I
don't run the make-release-tarball script except when testing the
script itself. CI makes and archives the tarballs. We don't release
any tarball without it being tested.

The purpose of the script is to out right fail when developer lie
about the dependencies or break them. I hold the developers
accountable to the deps, "Either say what you mean, or mean what you
say, because the script will not accept a discrepancy". We can make
many source package branches and source packages as we want since we
always have the tested tarball.

In the future, the test results and tarball will be at
reports.vapour.ws. We may also collect the test packages for others to
test. The are made by the publish-revision job, but I will break that
into small jobs for source, binary, tools, and publication jobs
http://juju-ci.vapour.ws:8080/job/publish-revision/
    http://juju-ci.vapour.ws:8080/job/publish-revision/438/

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui