From: Erdem G. <erd...@ya...> - 2009-03-06 08:31:51
|
Hi all, since I have no experience with the disctributed VCS so far, I was not in favor of that, but always, I take your considerations into account, I will have a look at Git and Hg, and then see if and how SourceForge supports that, then we can decide how to proceed with that, best regards, Erdem ________________________________ From: Edwin Commandeur <com...@gm...> To: gwt...@li... Sent: Tuesday, March 3, 2009 12:07:23 AM Subject: Re: [Gwt-openlayers-devl] Devl mailing list Hi all, I agree with Farrukh that it would be best to migrate to a distributed VCS directly, instead of first migrating to SVN first and then to a distributed VCS second. If we want a distributed VCS it's better to dive into it now, so we can get experienced with it. Also, Git is supported by SF (unlike Hg, as I am now aware). That said, I still have worries about Git on Windows, since my work laptop is a Windows machine. Does Farrukh or anyone else has experience with Git command line clients on windows? I would like to be able to interact with Git outside of Eclipse. The msysGit project looks promising, so I will definitely download that and give it a testdrive. If anyone has experience with Git on Windows, and can testify it works, then I would be all for Git. How about Erdem, and the others? I have good faith that all the major IDEs will be supporting Git, since Eclipse and IntelliJ already do. Should we however decide on SVN then I would be willing to do the migration. Greetings, Edwin 2009/3/2 Farrukh Najmi <fa...@we...> Just to be clear. You opt for migrating from CVS to svn then perhaps later to git or hg? Why not just stay with cvs until we go to git or hg? Why migrate twice? IMHO svn's advantages over cvs are modest. That said I will be fine with going to svn if that is a popular option and if someone else does the migration. Thanks. Erdem Gunay wrote: > First of all, thanks to Farrukh for letting us communicate through dev mailing list, > > at the moment, I prefer to stay with SVN, in the future once it is officially supported and many developers are used to git, or hg, we can move to that one, > > best regards, > > Erdem, > > > > ----- Original Message ---- > From: Farrukh Najmi <fa...@we...> > To: gwt...@li... > Sent: Sunday, March 1, 2009 3:30:46 PM > Subject: Re: [Gwt-openlayers-devl] Devl mailing list > > > Unfortunately, as Curtis reminded me, hg is not offered by SF. > > So the choice is between svn and git. I have used git enough to know > that it does work out of the box with a minor learning curve. I would > prefer git but like most of us I can live with svn. > > Are there other folks who would prefer to stay with svn rather than > learning git? > > Note that with IDE support for NetBeans and eclipse the learning curve > should not be that much of an issue. > > Thanks. > > Edwin Commandeur wrote: > >> Hi there, >> >> I am perfectly happy with SVN, which I think would already be a major >> improvement over CVS and would suit our needs fine, but I would also >> agree with using Hg. >> >> I have more confidence in Hg than in Git, because to my mind a VCS >> tool should just work, and not be so open ended as Git. >> >> Also, as a Java Developer I think about projects as Open JDK for which >> they are also using Hg, so I would be interested to learn about Hg >> more than about Git. >> >> Having not used any of the distributed VCS tools, I cannot talk from >> experience, but on the Git vs Mercurial comparison it is stated that >> "migrating from Subversion/CVS to git requires a lot of work. Linus >> has made it clear that he disagrees with the fundamental ideas behind >> Subversion/CVS" >> >> I have no idea if migrating from CVS to Mercurial is any easier, but >> that could also be a consideration to take into account. >> >> Greetings, >> Edwin >> >> >> gwt...@li... >> <mailto:gwt...@li...> >> >> 2009/3/1 Farrukh Najmi <fa...@we... >> <mailto:fa...@we...>> >> >> >> I have not used hg and have used git a little so can't say I have a >> strong opinion between the two DVCS tools. Here is a good blog >> comparing >> the two: >> >> <http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/> >> >> High order bit decision is whether we should do a more modern >> distributed version control system like git or hg instead of svn. >> So far >> it sounds like the opinions are in the YES camp. >> >> I can go with either hg or git. Lets see what others feel. Thanks. >> >> Aaron Novstrup wrote: >> > If you're going to switch to a DVCS, I'd recommend hg since >> AFAIK it's >> > better than git for cross-platform development. No strong >> preference, >> > though, just my two cents. >> > >> > Farrukh Najmi wrote: >> >> Dear team mates, >> >> >> >> Here is our list for the dev team to communicate. I will set us >> up on >> >> the other two lists (users, commits) shortly. >> >> >> >> I noticed that SF now offers git as a version control system (VCS). >> >> git was created by Linus of Linux fame and is used by projects like >> >> Linux. Its is better than svn and one of the best VCS available. >> >> >> >> What do folks think of using git instead of svn? The main advantage >> >> svn has is one of familiarity. However git has many advanced >> features >> >> beyond svn (distributed VCS being an important one). >> >> >> >> Here is a useful resource: >> >> >> >> <http://git.or.cz/gitwiki/GitSvnComparsion> >> >> >> >> Please share your thoughts on this. Thanks. >> >> >> >> >> > >> >> > > > -- Regards, Farrukh Web: http://www.wellfleetsoftware.com ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Gwt-openlayers-devl mailing list Gwt...@li... https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-devl |