On Fri, Feb 19, 2016 at 11:46 AM Nate Finch <[email protected]> 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 <[email protected]> > wrote: > >> On Fri, Feb 19, 2016 at 10:03 AM Ian Booth <[email protected]> >> 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 >>> [email protected] >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/juju-dev >>> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
