+1
Vincent
2012/9/5 Olivier Lamy ol...@apache.org:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move and more generally on git
Whilst it may work it's also rather horrible, unless every module in said
repository shares the same version number and gets released at the same time.
If however it's planned to go this route of a single repository, but separate
release cadences for modules, some rework and new releases of the
Is this not where the use of Review Board ( or preferably, Gerrit IMHO ) comes
into play, any patch/commit goes thru the code review system prior to being
accepted, and part of that review process is a required signoff that committer
X has a contribution license for the project.
On 12/09/2012,
2012/9/13 Mark Derricutt m...@talios.com:
Whilst it may work it's also rather horrible, unless every module in said
repository shares the same version number and gets released at the same time.
If however it's planned to go this route of a single repository, but separate
release cadences
To: Maven Developers List dev@maven.apache.org
Sent: Thursday, September 13, 2012 9:45 PM
Subject: Re: [VOTE] Move Maven projects sources to git
2012/9/13 Mark Derricutt m...@talios.com:
Whilst it may work it's also rather horrible, unless every module in said
repository shares the same version
Hi,
So it looks it was an interesting vote and topic with some
nice/various views. (seems people looks more interested than voting on
release :P )
The vote details are:
+1 (binding PMC)
krosenvold
sconnolly
aheritier
benson
milos
barrie
john casey
emmanuel venisse
herve boutemy
olamy
mark
/struberg/maven-scm-providers-git/commit/e670863b2b03e158c59f34af1fee20f91b2bd852
- Original Message -
From: Olivier Lamy ol...@apache.org
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Wednesday, September 5, 2012 1:04 PM
Subject: [VOTE] Move Maven projects sources to git
+1
Emmanuel
On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move
But GIT sucks a bit when it comes to projects like maven-shared and
maven-plugins which get released in portions. We already explained that with
long words and we might have found a compromise which doesn't hurt too badly.
But still it has to be verified if that works out.
Tagging the
: Tuesday, September 11, 2012 2:13 PM
Subject: Re: [VOTE] Move Maven projects sources to git
But GIT sucks a bit when it comes to projects like maven-shared and
maven-plugins which get released in portions. We already explained that with
long words and we might have found a compromise which
+1, and I'm willing to volunteer if you still need more people.
On 09/05/2012 06:04 AM, Olivier Lamy wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on
On 09/11/2012 07:13 AM, Kristian Rosenvold wrote:
But GIT sucks a bit when it comes to projects like maven-shared and
maven-plugins which get released in portions. We already explained that with
long words and we might have found a compromise which doesn't hurt too
badly. But still it has
Changing my vote to +1 based on Kristian and Mark's recent exchanges.
Wayne
On Thu, Sep 6, 2012 at 11:28 AM, Wayne Fay wayne...@gmail.com wrote:
[+1] Move to git scm
[0] No interest
[-1] don't move to git (please explain why)
+0.5
Sorry but I will be no help, I have little git experience
I don't think it's IF we should move to git, but WHEN and now seems to be
the right time.
+1
Robert
Op Tue, 11 Sep 2012 14:49:46 +0200 schreef Paul Gier pg...@redhat.com:
+1, and I'm willing to volunteer if you still need more people.
On 09/05/2012 06:04 AM, Olivier Lamy wrote:
Hi,
This
I'm +1
On Tue, Sep 11, 2012 at 1:39 PM, Robert Scholte rfscho...@apache.orgwrote:
I don't think it's IF we should move to git, but WHEN and now seems to be
the right time.
+1
Robert
Op Tue, 11 Sep 2012 14:49:46 +0200 schreef Paul Gier pg...@redhat.com:
+1, and I'm willing to volunteer
I think it would be a very pragmatic move to simply leave the
maven-plugins project unmigrated
until we have established documentation and tool support to a level
where we're happy with whatever solution we choose.
I think the only really disasterous version we could end up with is
the one which
+1 (non binding).
Willing to help. Git shows clear advantages over svn.
Le 5 sept. 2012 14:37, Garvin LeClaire garvin.lecla...@gmail.com a
écrit :
+1 (non-binding)
--
Regards,
Garvin LeClaire
garvin.lecla...@gmail.com
On Wed, Sep 5, 2012 at 8:33 AM, Anders Hammar and...@hammar.net
that we don't have any
devs of that kind around actively working on maven ;)
LieGrue,
strub
- Original Message -
From: Chris Graham chrisgw...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Thursday, September 6, 2012 2:33 AM
Subject: Re: [VOTE] Move Maven
Hi,
As Kristian said, there's already a Zillion articles referencing it.
Personnally, (DVCS advantage) I really like being able to work
locally/offline, going back and forth in the history and branches, *very
quickly*. Having no difficulty to navigate between ideas without much
burden.
Being able
[+1] Move to git scm
[0] No interest
[-1] don't move to git (please explain why)
+0.5
Sorry but I will be no help, I have little git experience except as an end user.
Wayne
-
To unsubscribe, e-mail:
+0
I personally don't have the git knowledge to be able to help, but I'm
interested in learning the new technology.
In my view the tooling for git is not yet as good as for SVN, but it's
getting there.
We have two important things to look out for:
1. Support for git at the ASF, and
the 'experiment' to be
successful.
LieGrue,
strub
- Original Message -
From: Dennis Lundberg denn...@apache.org
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Thursday, September 6, 2012 8:53 PM
Subject: Re: [VOTE] Move Maven projects sources to git
+0
I personally
On 09/05/2012 08:39 AM, Olivier Lamy wrote:
I'm a bit curious to see if that will increase externals contributions.
I think plain Git is only marginally more friendly for external contributors than Subversion. Yes you can create a local branch and update it against trunk changes, but
you
@maven.apache.org
Cc:
Sent: Thursday, September 6, 2012 9:35 PM
Subject: Re: [VOTE] Move Maven projects sources to git
On 09/05/2012 08:39 AM, Olivier Lamy wrote:
I'm a bit curious to see if that will increase externals contributions.
I think plain Git is only marginally more friendly
2012/9/6 Jesse Glick jgl...@cloudbees.com:
On 09/05/2012 08:39 AM, Olivier Lamy wrote:
I'm a bit curious to see if that will increase externals contributions.
I think plain Git is only marginally more friendly for external contributors
than Subversion. Yes you can create a local branch and
github pull requests can be accepted even though we are ASF hosted, in
fact github will automatically close the corresponding
pull request as the commit is pushed back through the git mirroring
from asf-github.com/apache. I think github is extremely
important, but they have also managed to be
same here
but I'm convinced git can help in some cases, like maintaining branches in
parallel
so I'm finally +1
Regards,
Hervé
Le jeudi 6 septembre 2012 20:53:39 Dennis Lundberg a écrit :
+0
I personally don't have the git knowledge to be able to help, but I'm
interested in learning the
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move and more generally on git Apache infrastructure. (if you
are volunteer you must say that
+1 and volunteer for infra help.
2012/9/5 Olivier Lamy ol...@apache.org:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move and more
+1 Will volunteer
Den 5. sep. 2012 kl. 13:04 skrev Olivier Lamy ol...@apache.org:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move
+1. Have no spare time ATM, so cannot volunteer even if I would love to
On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at
+1 and volunteer for infra help.
I'll find the opportunity to launch few more shells commands per day :-)
Arnaud
On Wed, Sep 5, 2012 at 1:25 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
+1. Have no spare time ATM, so cannot volunteer even if I would love to
On 5 September
On Wed, 5 Sep 2012 13:04:29 +0200
Olivier Lamy ol...@apache.org wrote:
+1, but can not be volunteer no time at all ATM.
Next month should be better to help you guys and do some code at last...
tony.
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to
-1 Non binding.
I have no desire to setup and learn new tools for no clearly apparent
advantages.
There appears to be multitude of ways that DSCM's can be configured. I'm
not sure if sufficient thought/discussion has been given to the way in
which it should/can be set up.
Where it is to be
+1
Il giorno 05/set/2012 13:04, Olivier Lamy ol...@apache.org ha scritto:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move and more
I think Olivier already replied to some points given few points where Git
is really interesting : performances, branches management ..
But yes there are skills to learn, it's not easy and the error is to think
that Git is like SVN
But it may be an opportunity to learn ?
On Wed, Sep 5, 2012 at
+1, git is far beyond being a 'fad'
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Wed, Sep 5, 2012 at 6:41 AM, Arnaud Héritier aherit...@gmail.com wrote:
I think Olivier already replied to some points given few points where Git
is really interesting : performances, branches management ..
The hosting bit is defined in context of apache, there is not much we
need to do in that respect. This dusussion has been on/off for quite a
few years, so I'm not entirely surprised if you haven't seen it all.
As for fad, I'm old enough to believe that version control systems
have their epochs.
+1 (non-binding)
But I don't have the hard-core git knowledge to help out in the move.
Would probably do more harm than good. :-)
/Anders
On Wed, Sep 5, 2012 at 2:19 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
The hosting bit is defined in context of apache, there is not much we
+1 (non-binding)
--
Regards,
Garvin LeClaire
garvin.lecla...@gmail.com
On Wed, Sep 5, 2012 at 8:33 AM, Anders Hammar and...@hammar.net wrote:
+1 (non-binding)
But I don't have the hard-core git knowledge to help out in the move.
Would probably do more harm than good. :-)
/Anders
On
I think Chris ask more what will that change for our projects for
community point.
Perso I'm a bit curious to see if that will increase externals contributions.
I don't want to do that only to ease life of private maven forkers.
But so this discussion must in a separate thread not in the vote
+1 binding can help
On Wed, Sep 5, 2012 at 7:45 AM, Jesse McConnell
jesse.mcconn...@gmail.com wrote:
+1, git is far beyond being a 'fad'
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Wed, Sep 5, 2012 at 6:41 AM, Arnaud Héritier aherit...@gmail.com wrote:
I think Olivier already
+1, cannot help unfortunatelely
Milos
On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on
It's not a matter of thinking that git is like SVN at all.
It's the exact opposite in fact; they are different, to the extent that it
entails a whole new approach.
We have a well resourced, well understood, well supported tool and mature
practices with our current SVN.
All I am saying is that
fwiw, i suspect most of us that have voted simply prefer working with
git over svn
certainly anyone that has had to manage branching and merging with svn
vs git would understand...it is simply better with git.
sorry you had management push you to use Hg, but git is a solid
upgrade over svn at
+0
S.
On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move and
Chris,
Just whom amongst us are you labeling 'a few immature devs'?
Many of us here have been using both git and svn, extensively, for
years now, and have a preference for git based on plenty of practical
experience. While git is new-ish at the ASF, it's official, and a
growing list of projects
2012/9/5 Chris Graham chrisgw...@gmail.com:
It's not a matter of thinking that git is like SVN at all.
It's the exact opposite in fact; they are different, to the extent that it
entails a whole new approach.
We have a well resourced, well understood, well supported tool and mature
I'm +0.5 on everything that currently has the trunk/tags/branches setup in SVN.
-1 on things that are not setup that way right now until more discussions and
agreement can be made on how that should be approached.
Really, I think we should just do Maven core and maybe one or two other simple
We only move things we are satisfied with. But we don't vote on each
item unless there turns out to be some real issues to solve.
Most of the maven projects already have excellent git repositories at
http://git.apache.org/,
for these it's just a modified scm url and the flip of a switch or two.
2012/9/5 Kristian Rosenvold kristian.rosenv...@gmail.com:
We only move things we are satisfied with. But we don't vote on each
item unless there turns out to be some real issues to solve.
Most of the maven projects already have excellent git repositories at
http://git.apache.org/,
Note:
+1
--
Regards,
Igor
On 12-09-05 7:04 AM, Olivier Lamy wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move and more generally on
+1 non binding
In terms of learning more about git, there are a LOT of free resources
available including books and other documentation as well as things like
live office hours at github and so on.
GitHub is also open sourcing all their training material so there will be
more as well.. and lots
No-one is using cvs anymore.
That's a wrong assumption, sad but true.
I still know companies which haven't invested in moving forward to a new
versioning system, because CVS still works good enough.
Investments is not only about the hardware and the investigation,
preparation and execution
On Wed, Sep 5, 2012 at 8:34 PM, Olivier Lamy ol...@apache.org wrote:
[+1] Move to git scm
[0] No interest
[-1] don't move to git (please explain why)
+1 (binding)
No capacity for volunteering to help :(
-
To unsubscribe,
+1 but have no time to volunteer at the moment.
On 9/5/12 6:04 AM, Olivier Lamy wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on Apache infra
for this move
If we applied the same logic back in 2004, we would still be on CVS.
Personally, I think Git affords us a lot of opportunity to streamline
the contribution process and a much cleaner way of working (patching,
rebasing, local branches, etc.)
I've switched to Git for all of the rest of what I
I knew someone would misread that.
I was not referring to anyone on this list. People on this list are at the
pointy end of the stick, although we have a spread of abilities, most are
in the upper end of the scale. The reason for this is simple. It's because
to do it because we like it, a passion
+1 I/we can volunteer.
-Original Message-
From: Stephane Nicoll [mailto:stephane.nic...@gmail.com]
Sent: Wednesday, September 05, 2012 9:21
To: Maven Developers List
Subject: Re: [VOTE] Move Maven projects sources to git
+0
S.
On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol
+0.5 if it makes devs or patchers lives easier
No time to help, and I'd like to see a clearer understanding of how we'll
convert non-t/b/t-layout repos before we end up with 50 repositories as others
have said.
BTW, if anyone is looking at doing that, I found the svn2git worked well for
60 matches
Mail list logo
