Re: [all] japicmp/parent

2019-01-20 Thread Gilles Sadowski
Le dim. 20 janv. 2019 à 04:15, Rob Tompkins a écrit : > > I think we may be at a place where we may want a new parent build because > japicmp 0.13 seems to work. @britter seems to want to use it in [collections] > (I’m a +1 to that). > > Also, @britter, @bodewig did some good work on the last

Re: [VOTE][RC2] Commons collections 4.3

2019-01-20 Thread Gilles Sadowski
Le dim. 20 janv. 2019 à 04:56, Maxim Solodovnik a écrit : > > I can see there is activity with replacing clirr with japicmp, maybe it > worth to hold this release until commons-parent v48 will be released? You are the manager. :-) Gilles > > On Sun, 20 Jan 2019 at 05:52, Gilles Sadowski

Re: [all] svn -> gitbox migration

2019-01-20 Thread sebb
On Sun, 20 Jan 2019 at 03:53, Rob Tompkins wrote: > > Hey guys, > > I’m curious if you saw my conversation with Chris Lambertus over in INFRA > about what to do with our SVN repos [1]? I’m not quite sure what to do now > that we have the vote [2], to move the repos over. It seems that they want

Re: [all] svn -> gitbox migration

2019-01-20 Thread Rob Tompkins
> On Jan 20, 2019, at 4:08 AM, sebb wrote: > >> On Sun, 20 Jan 2019 at 03:53, Rob Tompkins wrote: >> >> Hey guys, >> >> I’m curious if you saw my conversation with Chris Lambertus over in INFRA >> about what to do with our SVN repos [1]? I’m not quite sure what to do now >> that we have

Re: [all] svn -> gitbox migration

2019-01-20 Thread Gary Gregory
I think the simplest would be to migrate them all. Then we can forget all of that svn tree and mark it as read-only. Gary On Sun, Jan 20, 2019 at 6:48 AM Rob Tompkins wrote: > > > > On Jan 20, 2019, at 4:08 AM, sebb wrote: > > > >> On Sun, 20 Jan 2019 at 03:53, Rob Tompkins wrote: > >> > >>

Re: [all] svn -> gitbox migration

2019-01-20 Thread sebb
On Sun, 20 Jan 2019 at 13:44, Gary Gregory wrote: > > I think the simplest would be to migrate them all. Then we can forget all > of that svn tree and mark it as read-only. +1 It will make it easier to find things if they are all in one place. > Gary > > On Sun, Jan 20, 2019 at 6:48 AM Rob

fatal: Authentication failed for 'https://gitbox.apache.org/repos/asf/commons-collections.git/'

2019-01-20 Thread Gary Gregory
Oddly, I cannot push to collections' git repo: fatal: Authentication failed for ' https://gitbox.apache.org/repos/asf/commons-collections.git/' Did we miss something during the migration or is there something *I* need to do? Gary

Re: fatal: Authentication failed for 'https://gitbox.apache.org/repos/asf/commons-collections.git/'

2019-01-20 Thread Gary Gregory
Never mind, my bad. On Sun, Jan 20, 2019 at 9:11 AM Gary Gregory wrote: > Oddly, I cannot push to collections' git repo: > > fatal: Authentication failed for ' > https://gitbox.apache.org/repos/asf/commons-collections.git/' > > Did we miss something during the migration or is there something

[GitHub] CasualSuperman closed pull request #66: COLLECTIONS-709 Set Entry count to 0 after remove

2019-01-20 Thread GitBox
CasualSuperman closed pull request #66: COLLECTIONS-709 Set Entry count to 0 after remove URL: https://github.com/apache/commons-collections/pull/66 This is an automated message from the Apache Git Service. To respond to

Re: [VOTE][RC2] Commons collections 4.3

2019-01-20 Thread Gary Gregory
We might as well start with releasing fresh versions of our internal maven plugins, then commons-parent, then components... ;-) More work for the RM! :-) Gary On Sun, Jan 20, 2019 at 5:06 AM Gilles Sadowski wrote: > Le dim. 20 janv. 2019 à 04:56, Maxim Solodovnik a > écrit : > > > > I can see

Re: [all] svn -> gitbox migration

2019-01-20 Thread Rob Tompkins
> On Jan 20, 2019, at 8:57 AM, sebb wrote: > > On Sun, 20 Jan 2019 at 13:44, Gary Gregory wrote: >> >> I think the simplest would be to migrate them all. Then we can forget all >> of that svn tree and mark it as read-only. > > +1 > > It will make it easier to find things if they are all