Re: [wtp-incubator-dev] Migrate incubator projects to Git?

[David M Williams <david_williams@xxxxxxxxxx>]

I think this is a great idea with one
general word of advice, and one cautionary question. 

In general, plan out what your "retreat"
or back out plan might be. e..g what if you try it for 
a month or two and find that you just
can't get your work done, then what would happen? 
I assume you could move back to cvs?
(I'm just saying this should be known before hand, 
not that its likely to happen). 

A specific question, though, about builds.
I think this will imply you follow a particular 
system for builds ... right?  As
long as you all build on hudson with what ever system you want, 
that's fine and up to you. But, thinking
ahead, if you wanted to graduate and then be built along 
with the rest of WTP, someone will have
to step up and figure out how to do that. I'm sure 
there's multiple solutions ... I'm just
cautioning that I won't know how to "fit it in" to a 
WTP build. 

It is a great idea. I'll look forward
to hearing what you all think about the tools.

From:	David Carver <d_a_carver@xxxxxxxxx>
To:	WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date:	06/01/2010 04:48 PM
Subject:	[wtp-incubator-dev] Migrate incubator projects to Git?
Sent by:	wtp-incubator-dev-bounces@xxxxxxxxxxx

---

I'd like to toss out the idea that the WTP Incubator
move off of CVS and 
over to Git.  The eclipse webmasters put out a general call earlier
asking for interested projects to do the migration.   Since the code
in 
the incubator is pretty self contained, we could do this on a per 
component basis.   It would also give us a place as a group to test
out 
and figure out any migration issues that can occur and any build 
infrastructure changes that may need to occur as well.   The items
we 
learn here could help benefit the community as a whole.

There are some risks assummed by this move.  First while the eGit
plugin 
is improving drastically every day, it still doesn't have all the 
feature level support of the CVS client.   So those using git repos
would need to be willing to help out the eGit project and when necessary
move to command line for some items.   I suspect that eGit is going
to 
get to where it needs to be within the next 3 months.

There are build issues that will need to be addressed.   I'm planning
on 
migrating Vex's CI build on Hudson to Maven/Tycho, but keeping existing
functionality in place for the current WTP build.   The speed 
improvements I've seen in build times with maven have been pretty 
significant compared to other methods I've seen.   PsychoPath the
XPath 
2.0 processor went from an average of 20 minutes down to about 2 minutes
for a complete build.   XQuery I've seen similar results, but running
under 50 seconds.

Anyways, thought I'd toss this out to the incubator committers and get
some feedback.

Dave


_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev