>To: Maven Developers List
>Sent: Thursday, September 13, 2012 9:45 PM
>Subject: Re: [VOTE] Move Maven projects sources to git
>
>2012/9/13 Mark Derricutt :
>> Whilst it "may work" it's also rather horrible, unless every module in said
>> repository shares the s
2012/9/13 Mark Derricutt :
> 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
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,
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 th
+1
Vincent
2012/9/5 Olivier Lamy :
> 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 infrastruc
I'm +1
On Tue, Sep 11, 2012 at 1:39 PM, Robert Scholte wrote:
> 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 :
>
>
> +1, and I'm willing to volunteer if you still need more peo
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 :
+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
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 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 except as a
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 i
+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
t: 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 doesn't hur
> 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 w
+1
Emmanuel
On Wed, Sep 5, 2012 at 1:04 PM, 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 gene
+0 with a long explanation
I'm really a friend of GIT in general. As some might remember I am even the guy
who kicked off the GIT madness in maven land back in 2007 in the first place
[1].
But I'm also a friend of using the right tool for the right job.
GIT is great for projects which are no
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
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 smar
2012/9/6 Jesse Glick :
> 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 ag
he.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 Gi
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 still
r the 'experiment' to be
successful.
LieGrue,
strub
- Original Message -
> From: Dennis Lundberg
> To: Maven Developers List
> Cc:
> Sent: Thursday, September 6, 2012 8:53 PM
> Subject: Re: [VOTE] Move Maven projects sources to git
>
> +0
>
> I
+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 documentatio
> [+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: dev-unsubscr...@maven.a
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 t
ssume that we don't have any
devs of that kind around actively working on maven ;)
LieGrue,
strub
- Original Message -
> From: Chris Graham
> To: Maven Developers List
> Cc:
> Sent: Thursday, September 6, 2012 2:33 AM
> Subject: Re: [VOTE] Move Maven proje
+1 (non binding).
Willing to help. Git shows clear advantages over svn.
Le 5 sept. 2012 14:37, "Garvin LeClaire" a
écrit :
> +1 (non-binding)
>
> --
> Regards,
>
>
> Garvin LeClaire
> garvin.lecla...@gmail.com
>
>
> On Wed, Sep 5, 2012 at 8:33 AM, Anders Hammar wrote:
> > +1 (non-binding)
> >
>
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
+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
filter
+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.
>
&g
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
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 do
+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
On Wed, Sep 5, 2012 at 8:34 PM, Olivier Lamy 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, e-mail: dev-unsub
"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
+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 o
+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 git
2012/9/5 Kristian Rosenvold :
> 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: current ASF projects using git
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.
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
o
2012/9/5 Chris Graham :
> 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 cu
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 a
+0
S.
On Wed, Sep 5, 2012 at 1:04 PM, 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
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 thi
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
+1, cannot help unfortunatelely
Milos
On Wed, Sep 5, 2012 at 1:04 PM, 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
> f
+1 binding can help
On Wed, Sep 5, 2012 at 7:45 AM, Jesse McConnell
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 wrote:
>> I think Olivier already replied to some points given few point
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 thr
+1 (non-binding)
--
Regards,
Garvin LeClaire
garvin.lecla...@gmail.com
On Wed, Sep 5, 2012 at 8:33 AM, Anders Hammar 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 Wed, Sep 5, 2
+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
wrote:
> The hosting bit is defined in context of apache, there is not much we
> need to do in that respect
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, 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 wrote:
> I think Olivier already replied to some points given few points where Git
> is really interesting : performances, branches management ..
> But yes there ar
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:38
+1
Il giorno 05/set/2012 13:04, "Olivier Lamy" 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 generally
-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 hosted?
On Wed, 5 Sep 2012 13:04:29 +0200
Olivier Lamy 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 git (multiple
+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
+1. Have no spare time ATM, so cannot volunteer even if I would love to
On 5 September 2012 12:04, 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 volunteer
+1 Will volunteer
Den 5. sep. 2012 kl. 13:04 skrev Olivier Lamy :
> 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 gen
+1 and volunteer for infra help.
2012/9/5 Olivier Lamy :
> 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
58 matches
Mail list logo
