Re: [VOTE] Moving to Git...

2013-10-11 Thread Christian Grobmeier
On 11 Oct 2013, at 15:28, Ted Dunning wrote: I hate myself a bit for jumping in here, but as much as I prefer git, I really don't think that changing will make that much difference. Well, obviously I think it matters (see my other threads). The problem with commons is that people have much

Re: [VOTE] Moving to Git...

2013-10-11 Thread Ted Dunning
I hate myself a bit for jumping in here, but as much as I prefer git, I really don't think that changing will make that much difference. The problem with commons is that people have much more energy for interminable conversations about things that don't much matter (like this thread). People who

Re: [VOTE] Moving to Git...

2013-10-11 Thread Christian Grobmeier
+1 I consider this move to happen step by step and see only little risk if we start with a single component first. As the half of the world works with git meanwhile I see less risk in general too. On 10 Oct 2013, at 16:41, James Carman wrote: All, We have had some great discussions about

Re: [VOTE] Moving to Git...

2013-10-11 Thread Christian Grobmeier
On 10 Oct 2013, at 18:43, Jörg Schaible wrote: > Hi James, > > James Carman wrote: > >> Sorry, didn't understand your question. The Apache Camel team uses >> Git and they release maintenance versions all the time (I believe >> about 3 or 4 at a time sometimes when a bug fix gets merged down). >>

Re: [VOTE] Moving to Git...

2013-10-10 Thread Gilles
On Thu, 10 Oct 2013 11:58:58 -0400, James Carman wrote: On Thu, Oct 10, 2013 at 10:50 AM, Gilles wrote: -1 Some people have indicated that this move might not address the problem it is supposed to. No conclusive answer has been provided. What problem is that exactly? Perhaps that's not w

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
James Carman >> To: Commons Developers List >> Cc: >> Sent: Thursday, October 10, 2013 11:41 AM >> Subject: [VOTE] Moving to Git... >> >> All, >> >> We have had some great discussions about moving our SCM to Git. I >> think it's time to put

Re: [VOTE] Moving to Git...

2013-10-10 Thread Bruno P. Kinoshita
+1   Bruno P. Kinoshita http://kinoshita.eti.br http://tupilabs.com - Original Message - > From: James Carman > To: Commons Developers List > Cc: > Sent: Thursday, October 10, 2013 11:41 AM > Subject: [VOTE] Moving to Git... > > All, > > We have had s

Re: [VOTE] Moving to Git...

2013-10-10 Thread Jörg Schaible
Hi James, James Carman wrote: > Sorry, didn't understand your question. The Apache Camel team uses > Git and they release maintenance versions all the time (I believe > about 3 or 4 at a time sometimes when a bug fix gets merged down). > Here's a list of the current projects using Git: > > http

Re: [VOTE] Moving to Git...

2013-10-10 Thread Gary Gregory
On Thu, Oct 10, 2013 at 12:01 PM, James Carman wrote: > On Thu, Oct 10, 2013 at 11:09 AM, Gary Gregory wrote: >> >> Great point. Sounds like someone needs to experiment and show that it >> can be done. Since James started the vote,, perhaps he'd care to pick >> one Commons component and try to re

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
On Thu, Oct 10, 2013 at 11:09 AM, Gary Gregory wrote: > > Great point. Sounds like someone needs to experiment and show that it > can be done. Since James started the vote,, perhaps he'd care to pick > one Commons component and try to release through git... > How about this? I'm now on the Camel

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
On Thu, Oct 10, 2013 at 10:50 AM, Gilles wrote: > -1 > > Some people have indicated that this move might not address the problem > it is supposed to. No conclusive answer has been provided. > What problem is that exactly? Perhaps that's not well understood? -

Re: [VOTE] Moving to Git...

2013-10-10 Thread Jörg Schaible
James Carman wrote: > How is that any different than SVN? We have to release from branches > with SVN too. We don't copy our "maintenance" branches to trunk in > order to do releases. The SCM providers in Maven were not written with Git in mind, the Git provider is quite new compared to mature

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
Sorry, didn't understand your question. The Apache Camel team uses Git and they release maintenance versions all the time (I believe about 3 or 4 at a time sometimes when a bug fix gets merged down). Here's a list of the current projects using Git: https://git-wip-us.apache.org/repos/asf On Th

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
How is that any different than SVN? We have to release from branches with SVN too. We don't copy our "maintenance" branches to trunk in order to do releases. On Thu, Oct 10, 2013 at 11:09 AM, Gary Gregory wrote: > On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible > wrote: >> James Carman wrote:

Re: [VOTE] Moving to Git...

2013-10-10 Thread Gary Gregory
On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible wrote: > 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

Re: [VOTE] Moving to Git...

2013-10-10 Thread Gary Gregory
On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible wrote: > 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

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
The ASF has already set up "official" support for Git for their projects. These technical details have already been worked out. There are MANY other projects using Git already (around 1/3 I believe). On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible wrote: > James Carman wrote: > >> All, >> >> We

Re: [VOTE] Moving to Git...

2013-10-10 Thread Jörg Schaible
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! > > James -1 We have to ensure

Re: [VOTE] Moving to Git...

2013-10-10 Thread Emmanuel Bourg
Le 10/10/2013 16:57, Gary Gregory a écrit : > Could you please restart the thread with a [VOTE] in the subject? There is one though: http://www.mail-archive.com/dev@commons.apache.org/msg40574.html Emmanuel Bourg - To unsubscr

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
Gary, I actually did. You have to show details in Gmail to see it. For some reason it collapsed the two threads. Sorry for the confusion. There's a new thread already started. Thanks, James On Thu, Oct 10, 2013 at 10:57 AM, Gary Gregory wrote: > Could you please restart the thread with a [V

Re: [VOTE] Moving to Git...

2013-10-10 Thread Emmanuel Bourg
Le 10/10/2013 16:49, James Carman a écrit : > I'm going to start another thread. For me, in gmail, this got > combined with the [DISCUSS] thread and I don't want votes to get lost. > Consider this [VOTE] canceled! Romain, please vote again in the > other thread. Sorry, folks. At least in Thund

Re: [VOTE] Moving to Git...

2013-10-10 Thread Gary Gregory
Could you please restart the thread with a [VOTE] in the subject? Gary On Thu, Oct 10, 2013 at 10:41 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,

Re: [VOTE] Moving to Git...

2013-10-10 Thread Emmanuel Bourg
-0 I'm fine with SVN and the time sucked by the migration could be better spent coding the components (or reviewing the pending release candidates *cough*). That said, Git is now well supported by the tools I use, so I'm not opposed to the transition. Emmanuel Bourg Le 10/10/2013 16:41, James C

Re: [VOTE] Moving to Git...

2013-10-10 Thread Romain Manni-Bucau
@Gilles: that's right (and I'm part of people thinking this is not the main issue) but everybody seems happy to use git instead of svn so let's go *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/*

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
I'm going to start another thread. For me, in gmail, this got combined with the [DISCUSS] thread and I don't want votes to get lost. Consider this [VOTE] canceled! Romain, please vote again in the other thread. Sorry, folks. On Thu, Oct 10, 2013 at 10:41 AM, James Carman wrote: > All, > > We

Re: [VOTE] Moving to Git...

2013-10-10 Thread Gilles
On Thu, 10 Oct 2013 10:41:11 -0400, 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 Some people have indicated that this move might not addre

Re: [VOTE] Moving to Git...

2013-10-10 Thread Romain Manni-Bucau
+1 *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/10 James Carman > All, > > We h

Re: [VOTE] Moving to Git...

2013-10-10 Thread James Carman
Here's my +1 (binding) On Thu, Oct 10, 2013 at 10:41 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

[VOTE] Moving to Git...

2013-10-10 Thread 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! James --