Please merge master into your feature branches
Andrew Wilkins
andrew.wilkins at canonical.com
Fri Feb 19 04:04:03 UTC 2016
On Fri, Feb 19, 2016 at 11:46 AM Nate Finch <nate.finch at canonical.com>
wrote:
> So uh... how are we going to deliver patches to 1.25 if CI can't run it?
>
CI for 1.25 is unaffected. The CI scripts check the juju client version and
do things differently depending on that.
On Thu, Feb 18, 2016 at 9:48 PM Andrew Wilkins <andrew.wilkins at canonical.com>
> wrote:
>
>> On Fri, Feb 19, 2016 at 10:03 AM Ian Booth <ian.booth at canonical.com>
>> wrote:
>>
>>> FYI for folks developing feature branches for juju-core.
>>>
>>> juju-core master has been updated to include the first round of
>>> functionality to
>>> improve the bootstrap experience. The consequence of this is that CI
>>> scripts
>>> needed to be updated to match. This means that any feature branch which
>>> has not
>>> had master commit 294388 or later merged in will not work with CI and so
>>> will
>>> not be blessed for release.
>>>
>>
>> Further to this, please see the draft 2.0 release notes for instructions:
>> http://paste.ubuntu.com/15127859/
>>
>> If there's anything you can't figure out from that and/or command help,
>> please let us know so we can fix the docs.
>>
>> Cheers,
>> Andrew
>>
>>
>>>
>>> --
>>> Juju-dev mailing list
>>> Juju-dev at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160219/d12fe075/attachment.html>
More information about the Juju-dev
mailing list