Hi, 2009/3/15 Youness Alaoui <kakar...@kakaroto.homelinux.net>: > On Fri, Mar 13, 2009 at 09:02:04PM +0000, Stéphane Bisinger wrote: > > Yes indeed, but that's just the way we work.. we usually > develop, then we enter a feature-freeze period and then we > release...
Not just you, but most open source project works this way and those who don't usually have trouble... I was not questioning this ;) > Well, we do already work with branches and we did already > discuss this quite a while ago (from the time when we were > using CVS).. the general idea was that noone wanted to do > it, noone wanted to use branches, they looked overly > complicated and although we tried every tutorial available > we ended up not understanding how they work (remember, > CVS..) when we moved to SVN, we didn't really bother that > much from changing our no-branch methodology.. the way we > work is fine in my opinion. I know what you mean, the only reason I knew there were branches when I was using SVN/CVS is because you are encouraged to create a "branches" directory when creating a repo... And anyway with SVN using branches is basically a nightmare. Having worked a lot with git recently, branches have become an unvaluable tool, the kind of tool that makes me wonder how I could even make breakfast without it... > Yes, git... well, I use git for work everyday, and one thing > that I know for sure about git is that it's not easy to use > for everyone... Granted, git isn't as easy as SVN or CVS, but on the other hand it is also much more powerful. Of course this is a matter of tastes, mainly, both CVS and SVN can do the job. > SF having git now is good, but I don't think > it fits the way we work, and I think that noone is ready to > learn how to use git. > I think that SVN is really fit for our workflow and I don't > think it's a good idea to switch... This is an absolutely valid point... And I understand it perfectly, when we forked centericq and created centerim I was reluctant about the switch from CVS to git, it was my first approach with this tool and it was still really complicated (you had to use cogito back then). After some time spent using it, though, I began to understand it's full power and now I wouldn't go back for anything in the world. Of course this is me, it must work for you. > Besides, svn is already relatively easy to work with with > regards to branches, so i don't think there's anything that > warrants a migration to git. I have to disagree on this one, merging and managing branches in SVN is a lot more complicated than with git. The second best feature of git for me, after the great advantage of not having to rely on any central server, is the easy branching and merging. > Anyways, this is all just my personal opinion, maybe others > have different opinions than mine, so of course I don't mind > anyone disagreeing with me. Thanks for answering, I do not wish to change your habits, but just to highlight a possible issue and give you suggestions on a possible evolution. Other than that, it's up to you to decide whether the issue exists or not -- Stéphane ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
