[VOTE] Move Apache Commons to Git for SCM...

classic Classic list List threaded Threaded
64 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

[VOTE] Move Apache Commons to Git for SCM...

James Carman
All,

We have had some great discussions about moving our SCM to Git.  I
think it's time to put it to a vote.  So, here we go:

+1 - yes, move to Git
-1 - no, do not move to Git

The vote will be left open for 72 hours.  Go!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

James Carman
Here's my +1 (binding)

On Thu, Oct 10, 2013 at 10:50 AM, James Carman
<[hidden email]> wrote:
> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Romain Manni-Bucau
+1 - yes, move to Git

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/10/10 James Carman <[hidden email]>

> Here's my +1 (binding)
>
> On Thu, Oct 10, 2013 at 10:50 AM, James Carman
> <[hidden email]> wrote:
> > All,
> >
> > We have had some great discussions about moving our SCM to Git.  I
> > think it's time to put it to a vote.  So, here we go:
> >
> > +1 - yes, move to Git
> > -1 - no, do not move to Git
> >
> > The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Matt Benson-2
In reply to this post by James Carman
On Thu, Oct 10, 2013 at 9:50 AM, James Carman <[hidden email]>wrote:

> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
>
+1 (binding)

Matt



> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Mark Thomas
In reply to this post by James Carman
On 10/10/2013 15:50, James Carman wrote:
> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!

-1. I'm not convinced that the implications have been fully thought
through (the web site has to remain on svn for example) nor that this
migration will solve the problems it aims to solve.

I'd be much happier with doing a trial with one component first before
starting a wholesale migration.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Thomas Vandahl
In reply to this post by James Carman
On 10.10.13 16:50, James Carman wrote:
> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git

-1

I don't see any advantages.

Bye, Thomas.





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Benedikt Ritter-4
In reply to this post by James Carman
+1 (binding)

we already have the mirrors for all proper components, so we probably will
only have to deal with sandbox and the site/build stuff.
I'll help where I can.


2013/10/10 James Carman <[hidden email]>

> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Damjan Jovanovic
In reply to this post by Mark Thomas
-1 (binding), it's a big change, so let's try Mark's idea of one
component first.



On Thu, Oct 10, 2013 at 5:06 PM, Mark Thomas <[hidden email]> wrote:

> On 10/10/2013 15:50, James Carman wrote:
>> All,
>>
>> We have had some great discussions about moving our SCM to Git.  I
>> think it's time to put it to a vote.  So, here we go:
>>
>> +1 - yes, move to Git
>> -1 - no, do not move to Git
>>
>> The vote will be left open for 72 hours.  Go!
>
> -1. I'm not convinced that the implications have been fully thought
> through (the web site has to remain on svn for example) nor that this
> migration will solve the problems it aims to solve.
>
> I'd be much happier with doing a trial with one component first before
> starting a wholesale migration.
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Bruno P. Kinoshita
In reply to this post by James Carman
Looks like I've voted on the wrong thread, here's my vote

+1
 
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com


----- Original Message -----

> From: James Carman <[hidden email]>
> To: Commons Developers List <[hidden email]>
> Cc:
> Sent: Thursday, October 10, 2013 11:50 AM
> Subject: [VOTE] Move Apache Commons to Git for SCM...
>
> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

garydgregory
+1

Gary

On Thu, Oct 10, 2013 at 1:36 PM, Bruno P. Kinoshita
<[hidden email]> wrote:

> Looks like I've voted on the wrong thread, here's my vote
>
> +1
>
> Bruno P. Kinoshita
> http://kinoshita.eti.br
> http://tupilabs.com
>
>
> ----- Original Message -----
>> From: James Carman <[hidden email]>
>> To: Commons Developers List <[hidden email]>
>> Cc:
>> Sent: Thursday, October 10, 2013 11:50 AM
>> Subject: [VOTE] Move Apache Commons to Git for SCM...
>>
>> All,
>>
>> We have had some great discussions about moving our SCM to Git.  I
>> think it's time to put it to a vote.  So, here we go:
>>
>> +1 - yes, move to Git
>> -1 - no, do not move to Git
>>
>> The vote will be left open for 72 hours.  Go!
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Luc Maisonobe
In reply to this post by Damjan Jovanovic
Le 10/10/2013 19:27, Damjan Jovanovic a écrit :
> -1 (binding), it's a big change, so let's try Mark's idea of one
> component first.

+1. I see a lot of advantages. The first one is in branches merging
which could help for experimental stuff, the second is in getting
contributions (for example large ones like that of Evan), and the third
is in the use tooling.

But I also agree a first step with one component would be easier for
most people. Git is not simple to learn.

Luc


>
>
>
> On Thu, Oct 10, 2013 at 5:06 PM, Mark Thomas <[hidden email]> wrote:
>> On 10/10/2013 15:50, James Carman wrote:
>>> All,
>>>
>>> We have had some great discussions about moving our SCM to Git.  I
>>> think it's time to put it to a vote.  So, here we go:
>>>
>>> +1 - yes, move to Git
>>> -1 - no, do not move to Git
>>>
>>> The vote will be left open for 72 hours.  Go!
>>
>> -1. I'm not convinced that the implications have been fully thought
>> through (the web site has to remain on svn for example) nor that this
>> migration will solve the problems it aims to solve.
>>
>> I'd be much happier with doing a trial with one component first before
>> starting a wholesale migration.
>>
>> Mark
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

James Carman
We could migrate our new release testing project (commons-canary :)
first.  Get the kinks worked out using it.  Then, we migrate the rest
of the projects.

On Thu, Oct 10, 2013 at 3:13 PM, Luc Maisonobe <[hidden email]> wrote:

> Le 10/10/2013 19:27, Damjan Jovanovic a écrit :
>> -1 (binding), it's a big change, so let's try Mark's idea of one
>> component first.
>
> +1. I see a lot of advantages. The first one is in branches merging
> which could help for experimental stuff, the second is in getting
> contributions (for example large ones like that of Evan), and the third
> is in the use tooling.
>
> But I also agree a first step with one component would be easier for
> most people. Git is not simple to learn.
>
> Luc
>
>
>>
>>
>>
>> On Thu, Oct 10, 2013 at 5:06 PM, Mark Thomas <[hidden email]> wrote:
>>> On 10/10/2013 15:50, James Carman wrote:
>>>> All,
>>>>
>>>> We have had some great discussions about moving our SCM to Git.  I
>>>> think it's time to put it to a vote.  So, here we go:
>>>>
>>>> +1 - yes, move to Git
>>>> -1 - no, do not move to Git
>>>>
>>>> The vote will be left open for 72 hours.  Go!
>>>
>>> -1. I'm not convinced that the implications have been fully thought
>>> through (the web site has to remain on svn for example) nor that this
>>> migration will solve the problems it aims to solve.
>>>
>>> I'd be much happier with doing a trial with one component first before
>>> starting a wholesale migration.
>>>
>>> Mark
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Phil Steitz
In reply to this post by James Carman
The "binding" annotations on this thread kind of bug me here - we
should be deciding this kind of thing by community consensus.
"Binding" is only meaningful in release votes and VOTE-ing in
general should be a last resort rather than early step in getting to
consensus.  I have tried to keep up with the threads but have yet to
see a really clear rationale for the move.  It would help me
personally get on board with allocating some of my own scarce
volunteering time to this if I someone could summarize what exactly
we will get out of it.

Phil

On 10/10/13 7:50 AM, James Carman wrote:

> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Oliver Heger-3
In reply to this post by James Carman
+1 to git in general, however, I also prefer the approach to do the move
in a more careful way, i.e. experimenting with single components first.

Oliver

Am 10.10.2013 16:50, schrieb James Carman:

> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Olivier Lamy
In reply to this post by James Carman
Even I like git and use it daily, I will vote +0,5.

Why other apache projects need to have their own commons-csv
repackaged release? why tomcat need to use a svn:external on dbcp
instead of a released version? why servicemix need to repackage all
commons jar to have proper osgi bundles?

I simply believe moving to git won't fix those problems about the too
complicated release process which scare folks here to try releasing a
component!!
So no release happen at the end....


On 11 October 2013 01:50, James Carman <[hidden email]> wrote:

> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Phil Steitz


> On Oct 10, 2013, at 4:41 PM, Olivier Lamy <[hidden email]> wrote:
>
> Even I like git and use it daily, I will vote +0,5.
>
> Why other apache projects need to have their own commons-csv
> repackaged release? why tomcat need to use a svn:external on dbcp
> instead of a released version? why servicemix need to repackage all
> commons jar to have proper osgi bundles?
>
> I simply believe moving to git won't fix those problems about the too
> complicated release process which scare folks here to try releasing a
> component!!
> So no release happen at the end....
>
I agree that the release process is certainly a problem; but the big problem IMO is just too many components for too few really active committers.  Once we actually have something ready to release, we have generally been able to fumble our way through the process.  The problem is getting there.  

I think the best thing we can do is focus on getting some things ready for release.  I will help on pool, DBCP, math.  I won't rob Mark of the oppty to rm pool2, but will help ;). All are welcome to join the fun cleaning up the docs and other loose ends on that and then dbcp2.  

Who wants to step up to drive some other things  to release?

Phil

>
>> On 11 October 2013 01:50, James Carman <[hidden email]> wrote:
>> All,
>>
>> We have had some great discussions about moving our SCM to Git.  I
>> think it's time to put it to a vote.  So, here we go:
>>
>> +1 - yes, move to Git
>> -1 - no, do not move to Git
>>
>> The vote will be left open for 72 hours.  Go!
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

James Carman
Matt and I will probably have proxy2 ready very soon, too


On Thu, Oct 10, 2013 at 8:10 PM, Phil Steitz <[hidden email]> wrote:

>
>
>> On Oct 10, 2013, at 4:41 PM, Olivier Lamy <[hidden email]> wrote:
>>
>> Even I like git and use it daily, I will vote +0,5.
>>
>> Why other apache projects need to have their own commons-csv
>> repackaged release? why tomcat need to use a svn:external on dbcp
>> instead of a released version? why servicemix need to repackage all
>> commons jar to have proper osgi bundles?
>>
>> I simply believe moving to git won't fix those problems about the too
>> complicated release process which scare folks here to try releasing a
>> component!!
>> So no release happen at the end....
>>
> I agree that the release process is certainly a problem; but the big problem IMO is just too many components for too few really active committers.  Once we actually have something ready to release, we have generally been able to fumble our way through the process.  The problem is getting there.
>
> I think the best thing we can do is focus on getting some things ready for release.  I will help on pool, DBCP, math.  I won't rob Mark of the oppty to rm pool2, but will help ;). All are welcome to join the fun cleaning up the docs and other loose ends on that and then dbcp2.
>
> Who wants to step up to drive some other things  to release?
>
> Phil
>>
>>> On 11 October 2013 01:50, James Carman <[hidden email]> wrote:
>>> All,
>>>
>>> We have had some great discussions about moving our SCM to Git.  I
>>> think it's time to put it to a vote.  So, here we go:
>>>
>>> +1 - yes, move to Git
>>> -1 - no, do not move to Git
>>>
>>> The vote will be left open for 72 hours.  Go!
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Mark Thomas
In reply to this post by Olivier Lamy
On 11/10/2013 00:41, Olivier Lamy wrote:

<snip/>

> Why other apache projects need to have their own commons-csv
> repackaged release? why tomcat need to use a svn:external on dbcp
> instead of a released version?

Tomcat does not use an svn:external of any Commons component.

Tomcat releases depend only on released versions of DBCP  (excluding the
8.0.x release candidates which are using snapshots of Pool 2 and DBCP 2
and will switch to released versions before the first stable 8.0.x
release) .

Tomcat does have package renamed versions of Pool, DBCP, Digester,
Logging, FileUpload, Codec and BCEL. Some of these are via svn cp, some
(including DBCP) are scripted from the released source tarballs.

Tomcat depends directly on Daemon.

There are several reasons why Tomcat does not, can not and will not ship
Commons JARs directly:
- the package rename is necessary to avoid potential conflicts if a web
application ships with the same jar
- sometimes Tomcat only needs a few classes from a much larger JAR

None of the reasons have anything to do with Commons's choice of git vs
svn, Ant vs Maven or the frequency of releases.

There is nothing that Commons's could do that would remove the need for
Tomcat to repackage these JARS and enable Tomcat to simply ship the
released JARs directly.

There is nothing that Commons's could do to make it easier for Tomcat to
consume these artefacts (if there was, I'd have done it already).

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Ralph Goers
In reply to this post by Mark Thomas
I am +1 on using git but I won't be able to help with the changes that will need to be made so I am voting +0.  

FWIW, I don't think git really "solves" anything. It will fix a perception problem and it will make it easier to do distributed development.

Ralph


On Oct 10, 2013, at 8:06 AM, Mark Thomas <[hidden email]> wrote:

> On 10/10/2013 15:50, James Carman wrote:
>> All,
>>
>> We have had some great discussions about moving our SCM to Git.  I
>> think it's time to put it to a vote.  So, here we go:
>>
>> +1 - yes, move to Git
>> -1 - no, do not move to Git
>>
>> The vote will be left open for 72 hours.  Go!
>
> -1. I'm not convinced that the implications have been fully thought
> through (the web site has to remain on svn for example) nor that this
> migration will solve the problems it aims to solve.
>
> I'd be much happier with doing a trial with one component first before
> starting a wholesale migration.
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Move Apache Commons to Git for SCM...

Christian Grobmeier
In reply to this post by James Carman
+1

let's move on step by step.

On 10 Oct 2013, at 16:50, James Carman wrote:

> All,
>
> We have had some great discussions about moving our SCM to Git.  I
> think it's time to put it to a vote.  So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left open for 72 hours.  Go!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]


---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

1234