Re: [jgroups-dev] Moving JGroups from CVS to Git ?

> > BTW, you may consider creating a Github JGroups 'Project'. I wouldn't
> wait
> > for 3.0 ...
>
> What do you mean ? I've already created it at
> github.com/belaban/jgroups. But it's currently only experimental, we're
> still using CVS.
>
> Sorry, I said 'project', I meant to say 'Organization'. This could help:
http://support.github.com/discussions/repos/1173-registering-a-project-for-an-organization

An 'Organization' can give you the ability to manage commit privileges to
your contributors, although I have to tell you, with Git, a contributor
doesn't really need commit privileges, [s]he can just send you pull
requests. A release manager may need commit privileges though, and you can
manage that with Github's 'organizations'.


BTW: is there a way of preserving the commit history of CVS, when
> switching to Git ? I know this can be done for Subversion... I guess
> I'll have to finish the Git book before asking stupid questions ! :-)
>
> I've used svn2git and it preserved all history, branches, tags, etc. I just
had to create a simple 'authors' mapping file.

It seems there's also an cvs2git (http://cvs2svn.tigris.org/cvs2git.html).

Yesterday, I came across Eric Raymond's reposurgeon project that could be
good to have in mind, if required (http://esr.ibiblio.org/?p=2718).

I noticed that you now have maven support, is maven the preferred method to
build JGroups now or you still use ant?

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev

_______________________________________________
Javagroups-development mailing list