Either updated vendoring (looks like new tooling rather than being handled in go - and may still require a restructure of the repo), or https://github.com/apache/brooklyn-client/pull/11 will need to go in to ensure we're building the latest client (theres also a minor update to the help output in https://github.com/apache/brooklyn-client/pull/10) that we should include.
On Tue, 22 Mar 2016 at 14:20 Geoff Macartney < [email protected]> wrote: > I would like to look into replacing the use of godep in brooklyn-client in > favour of Go 1.6 vendoring, if that’s possible, especially because of > John’s PR https://github.com/apache/brooklyn-client/pull/11. > > Geoff > > > ———————————————————— > Gnu PGP key - http://is.gd/TTTTuI > > > > On 18 Mar 2016, at 09:55, Alex Heneveld <[email protected]> > wrote: > > > > > > Thomas is nearly done with a fantastic wizard to define locations, and > there are several PR's to be merged after that is in, and then I think > let's do a release! > > > > --A > > > > > > On 18/03/2016 09:37, Geoff Macartney wrote: > >> +1 > >> > >> > >> ———————————————————— > >> Gnu PGP key - http://is.gd/TTTTuI > >> > >> > >>> On 15 Mar 2016, at 14:37, Richard Downer <[email protected]> wrote: > >>> > >>> All, > >>> > >>> It's about time we had a new release of Apache Brooklyn - our first as > >>> a graduated TLP. We have lots of great new features to share :-) > >>> > >>> Is there anything that we know about that would block a release? > >>> > >>> Are there any outstanding or imminent PRs that would be highly > >>> desirable for a release? > >>> > >>> If we're in a good position it'd be great to get this kicked off in > >>> the next day or two. I've been going over the release scripts and > >>> documentation and fixing them for our TLP status, multiple new repos > >>> and our new distributable artifacts and I think I'm just about ready > >>> to push the "release candidate" button, if we think that the project > >>> is in a releasable state? > >>> > >>> Richard. > >> > > > >
