[VOTE] Moving to Git...

classic Classic list List threaded Threaded
48 messages Options
123
Reply | Threaded
Open this post in threaded view
|

[VOTE] Moving to Git...

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

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

Romain Manni-Bucau
+1

*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]>

> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

James Carman
In reply to this post by James Carman
Here's my +1 (binding)

On Thu, Oct 10, 2013 at 10:41 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!
>
> James

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

James Carman
In reply to this post by 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
<[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!
>
> James

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

Gilles Sadowski
In reply to this post by James Carman
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 address the problem
it is supposed to. No conclusive answer has been provided.


Regards,
Gilles


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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

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 <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 Gilles <[hidden email]>

> 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 address the problem
> it is supposed to. No conclusive answer has been provided.
>
>
> Regards,
> Gilles
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<[hidden email]>
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

Emmanuel Bourg-3
In reply to this post by James Carman
-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 Carman a écrit :

> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


signature.asc (851 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

garydgregory
In reply to this post by James Carman
Could you please restart the thread with a [VOTE] in the subject?

Gary

On Thu, Oct 10, 2013 at 10:41 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!
>
> James
>
> ---------------------------------------------------------------------
> 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] Moving to Git...

Emmanuel Bourg-3
In reply to this post by James Carman
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 Thunderbird the vote thread is distinct.

Emmanuel Bourg


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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

James Carman
In reply to this post by garydgregory
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 <[hidden email]> wrote:

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

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

Emmanuel Bourg-3
In reply to this post by garydgregory
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@.../msg40574.html

Emmanuel Bourg


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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

Jörg Schaible-3
In reply to this post by James Carman
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 before that our tooling works with Git and that we stay
compliant to ASF rules:

- Release from a Git branch (if we start increasing major versions more
frequently, we will have soon the requirement for maintenance releases).
AFAICS there are still problems for Maven.
- Someone raised the question about the shared stuff like site ... is that
solved?
- Which Git server has the master? At Apache? At Github? If Github, legal
consequences? If Apache, automated sync with Github?

No objection on the switch in general though.

Cheers,
Jörg




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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

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
<[hidden email]> 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 left open for 72 hours.  Go!
>>
>> James
>
>
> -1
>
> We have to ensure before that our tooling works with Git and that we stay
> compliant to ASF rules:
>
> - Release from a Git branch (if we start increasing major versions more
> frequently, we will have soon the requirement for maintenance releases).
> AFAICS there are still problems for Maven.
> - Someone raised the question about the shared stuff like site ... is that
> solved?
> - Which Git server has the master? At Apache? At Github? If Github, legal
> consequences? If Apache, automated sync with Github?
>
> No objection on the switch in general though.
>
> Cheers,
> Jörg
>
>
>
>
> ---------------------------------------------------------------------
> 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] Moving to Git...

garydgregory
In reply to this post by Jörg Schaible-3
On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible
<[hidden email]> 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 left open for 72 hours.  Go!
>>
>> James
>
>
> -1
>
> We have to ensure before that our tooling works with Git and that we stay
> compliant to ASF rules:
>
> - Release from a Git branch (if we start increasing major versions more
> frequently, we will have soon the requirement for maintenance releases).
> AFAICS there are still problems for Maven.
> - Someone raised the question about the shared stuff like site ... is that
> solved?
> - Which Git server has the master? At Apache?

Of course at Apache. Why anywhere else? There are plenty of projects
already at git.apache.org that are mirrored to GitHub. There is an
established precedent. It looks Commons projects are mirrored from SVN
to our Git server already.

Gary

At Github? If Github, legal

> consequences? If Apache, automated sync with Github?
>
> No objection on the switch in general though.
>
> Cheers,
> Jörg
>
>
>
>
> ---------------------------------------------------------------------
> 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] Moving to Git...

garydgregory
In reply to this post by Jörg Schaible-3
On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible
<[hidden email]> 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 left open for 72 hours.  Go!
>>
>> James
>
>
> -1
>
> We have to ensure before that our tooling works with Git and that we stay
> compliant to ASF rules:
>
> - Release from a Git branch (if we start increasing major versions more
> frequently, we will have soon the requirement for maintenance releases).
> AFAICS there are still problems for Maven.

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...

Gary

> - Someone raised the question about the shared stuff like site ... is that
> solved?
> - Which Git server has the master? At Apache? At Github? If Github, legal
> consequences? If Apache, automated sync with Github?
>
> No objection on the switch in general though.
>
> Cheers,
> Jörg
>
>
>
>
> ---------------------------------------------------------------------
> 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] Moving to Git...

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 <[hidden email]> wrote:

> On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible
> <[hidden email]> 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 left open for 72 hours.  Go!
>>>
>>> James
>>
>>
>> -1
>>
>> We have to ensure before that our tooling works with Git and that we stay
>> compliant to ASF rules:
>>
>> - Release from a Git branch (if we start increasing major versions more
>> frequently, we will have soon the requirement for maintenance releases).
>> AFAICS there are still problems for Maven.
>
> 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...
>
> Gary
>
>> - Someone raised the question about the shared stuff like site ... is that
>> solved?
>> - Which Git server has the master? At Apache? At Github? If Github, legal
>> consequences? If Apache, automated sync with Github?
>>
>> No objection on the switch in general though.
>>
>> Cheers,
>> Jörg
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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]
>

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

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 Thu, Oct 10, 2013 at 11:12 AM, James Carman
<[hidden email]> 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.
>
> On Thu, Oct 10, 2013 at 11:09 AM, Gary Gregory <[hidden email]> wrote:
>> On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible
>> <[hidden email]> 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 left open for 72 hours.  Go!
>>>>
>>>> James
>>>
>>>
>>> -1
>>>
>>> We have to ensure before that our tooling works with Git and that we stay
>>> compliant to ASF rules:
>>>
>>> - Release from a Git branch (if we start increasing major versions more
>>> frequently, we will have soon the requirement for maintenance releases).
>>> AFAICS there are still problems for Maven.
>>
>> 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...
>>
>> Gary
>>
>>> - Someone raised the question about the shared stuff like site ... is that
>>> solved?
>>> - Which Git server has the master? At Apache? At Github? If Github, legal
>>> consequences? If Apache, automated sync with Github?
>>>
>>> No objection on the switch in general though.
>>>
>>> Cheers,
>>> Jörg
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

Jörg Schaible-3
In reply to this post by James Carman
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 Svn provider and there have been
(also recently) reports form people that have problems to release from
branch with Maven.

It's *not* a problem of Git, it might be a problem with the tooling.

- Jörg


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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

James Carman
In reply to this post by Gilles Sadowski
On Thu, Oct 10, 2013 at 10:50 AM, Gilles <[hidden email]> 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?

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

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Moving to Git...

James Carman
In reply to this post by garydgregory
On Thu, Oct 10, 2013 at 11:09 AM, Gary Gregory <[hidden email]> 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 PMC.  How about I offer to be a
release manager for a maintenance release of Camel?  This way, I can
learn from a working git-based project about how they do it and bring
that knowledge back to us.  The instructions appear to just use the
standard maven release plugin.  We can "borrow" stuff from their Maven
setup of we want.

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

123