I agree with you Mark. I would cherry-pick only the fix for vagrant. On Fri, 20 Oct 2017 at 09:46 Duncan Grant <[email protected]> wrote:
> +1 (non-binding) > > > On Fri, 20 Oct 2017 at 09:44 Mark McKenna <[email protected]> wrote: > > > +1 > > > > IMO 0.12.1 should only contain this fix > > > > *Mark McKenna* > > > > *Twitter ::* @m4rkmckenna <https://twitter.com/m4rkmckenna> > > > > *Github :: *m4rkmckenna <https://github.com/m4rkmckenna> > > > > *PGP :: A7A9 24DE 638C 681A 8DEA FAD4 2B5D C759 B1EB 76A7 > > <https://pgp.mit.edu/pks/lookup?op=get&search=0x2B5DC759B1EB76A7>* > > > > On 19 October 2017 at 16:12, Richard Downer <[email protected]> wrote: > > > > > +1 > > > > > > On 19 October 2017 at 16:07, Thomas Bouron > <thomas.bouron@cloudsoftcorp. > > > com> > > > wrote: > > > > > > > Hi all > > > > > > > > A couple a people on IRC and the ML had issues with > `brooklyn-vagrant`. > > > > This is unfortunately broken in Brooklyn 0.12.0, but it is the main > > > > installation method that we promote on the Brooklyn website. > > > > > > > > As a new user, this can be a very frustrating first experience with > > > > Brooklyn which, IMO, does not send the right message. > > > > > > > > For this reason, I think we should do a Brooklyn 0.12.1 release as > soon > > > as > > > > possible. > > > > > > > > Let us know your opinions and if there are no other outstanding > > problems. > > > > > > > > Best. > > > > -- > > > > > > > > Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation • > > > > https://cloudsoft.io/ > > > > Github: https://github.com/tbouron > > > > Twitter: https://twitter.com/eltibouron > > > > > > > > > > -- Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation • https://cloudsoft.io/ Github: https://github.com/tbouron Twitter: https://twitter.com/eltibouron
