Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Gilles
On Fri, 28 Dec 2018 14:00:48 -0500, Rob Tompkins wrote: On Dec 28, 2018, at 1:31 PM, Gilles wrote: On Fri, 28 Dec 2018 13:18:41 -0500, Rob Tompkins wrote: Yes. I agree that makes sense. It is a considerable amount of work to do that migration in a single go. So, I’m not sure if we should go

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Gary Gregory
It all depends if one brave soul wants to do all that at once ;-) not me in the near term... Gary On Fri, Dec 28, 2018, 13:18 Rob Tompkins Yes. I agree that makes sense. It is a considerable amount of work to do > that migration in a single go. So, I’m not sure if we should go at it > piecemeal

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Rob Tompkins
> On Dec 28, 2018, at 1:31 PM, Gilles wrote: > > On Fri, 28 Dec 2018 13:18:41 -0500, Rob Tompkins wrote: >> Yes. I agree that makes sense. It is a considerable amount of work to >> do that migration in a single go. So, I’m not sure if we should go at >> it piecemeal or as a complete lump of wo

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Gilles
On Fri, 28 Dec 2018 13:18:41 -0500, Rob Tompkins wrote: Yes. I agree that makes sense. It is a considerable amount of work to do that migration in a single go. So, I’m not sure if we should go at it piecemeal or as a complete lump of work. -Rob On Dec 28, 2018, at 11:41 AM, Jochen Wiedmann wr

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Rob Tompkins
Yes. I agree that makes sense. It is a considerable amount of work to do that migration in a single go. So, I’m not sure if we should go at it piecemeal or as a complete lump of work. -Rob > On Dec 28, 2018, at 11:41 AM, Jochen Wiedmann > wrote: > > Weren't we going to fo that for *all* of

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Jochen Wiedmann
Weren't we going to fo that for *all* of our projects? On Fri, Dec 28, 2018 at 4:17 PM Pascal Schumacher wrote: > > +1 > > Am 28.12.2018 um 15:51 schrieb Rob Tompkins: > > After doing the 1.12 release I propose we move commons-codec to gitbox. > > This is a [LAZY] consensus [VOTE] for doing such

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Pascal Schumacher
+1 Am 28.12.2018 um 15:51 schrieb Rob Tompkins: After doing the 1.12 release I propose we move commons-codec to gitbox. This is a [LAZY] consensus [VOTE] for doing such after I get through the release. This [LAZY][VOTE] will be open for at least 72 hours form now. Cheers, -Rob ---

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Gary Gregory
+1 Gary On Fri, Dec 28, 2018, 09:51 Rob Tompkins After doing the 1.12 release I propose we move commons-codec to gitbox. > This is a [LAZY] consensus [VOTE] for doing such after I get through the > release. This [LAZY][VOTE] will be open for at least 72 hours form now. > > Cheers, > -Rob > -

[VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

2018-12-28 Thread Rob Tompkins
After doing the 1.12 release I propose we move commons-codec to gitbox. This is a [LAZY] consensus [VOTE] for doing such after I get through the release. This [LAZY][VOTE] will be open for at least 72 hours form now. Cheers, -Rob --