The whole offline advantage of git is largely irrelevant, IMO. The big win is the improved workflow. It is far easier to make large patches via the git/github model and submit via pull-requests than via patches attached to a bug entry. I've done this quite a few times over the past year, and github really is a huge win here, IMO.
On Tue, Mar 5, 2013 at 7:09 PM, Alex O'Ree <[email protected]> wrote: > I personally prefer svn. I don't "git" it. What are the requirement > for version control besides...well, version control in the context of > jUDDI? Git is handy for getting the complete version history offline, > but that point is pretty moot considering half of the internet is > downloaded during the maven build process. It's a bit faster for > certain actions and its useful for localized version control. SVN's > advantage is that it is integrated with just about everything out > there for software development. Just my two cents. I'll use whatever > the rest of you all want > > On Tue, Mar 5, 2013 at 5:52 PM, Jesse Sightler <[email protected]> > wrote: > > I hope this happens... I think it would be very good for the project. > > > > > > On Tue, Mar 5, 2013 at 5:32 PM, Kurt T Stam <[email protected]> wrote: > >> > >> Hi guys, > >> > >> What do you think about moving our repo from svn to git? Once it's on > >> git.apache.org we can mirror it on github, and it will make it much > easier > >> for people to contribute code, even if they are not (yet) committers on > the > >> project. > >> > >> --Kurt > > > > >
