On Fri, Mar 13, 2009 at 09:02:04PM +0000, Stéphane Bisinger wrote: > Hi, > Hi,
> 2009/3/13 Youness Alaoui <kakar...@kakaroto.homelinux.net>: > > 2 - We are currently trying to get amsn 0.98 released so the > > TODO list and bugs should be fixed... that's I think our top > > priority... It also basically means that we want bugfixes > > and we don't want to add new features that might add bugs... > > > Since it is not the first time I see such a scenario arising on this > mailing list, I think you really need to use branches. I do understand > that with SVN branches are hard to manage, but it's not the first time > I see some development held back because you have to concentrate on > getting 0.98 out. Yes indeed, but that's just the way we work.. we usually develop, then we enter a feature-freeze period and then we release... we already worked with branches when we want to develop something new before a release, it's been done and it's ok, but we rarely need it... > I'm not blaming anyone for this, it is absolutely > right to avoid introducing new features until 0.98 is out, but that's > why a branch would be useful: I fear that by rejecting contributions > for this reason could restrain some people from doing further > contributions, thinning the developing workforce. Well, actually no, without a feature freeze, we end up with new features all the time and we can never get to a stable point.. also, when someone has some time, he gets to do some bugfixing instead of introducing new bugs... a clear "Feature-freeze period" helps us advance further towards a new release... > Of course I understand that there might be technical difficulties, or > other problems of another nature and that you already discussed this > opting for no branches, but anyway I feel it worth letting you know > what I could observe from the outside. 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. We currently use branches for every release we make (so we can have bugfix releases later), and we did create some branches for some specific work (video_conf branch, purolator branch, etc...) but in general, the one trunk SVN way seems to work fine for us... > > Since SourceForge recently introduced support to git, I'm wondering > what are your feelings about it. It could solve easily the branching > problem, but it would of course need re-training on your part on how > to use the tool correctly. If you are not familiar with it, I could > write a guide on your Wiki on how to do development on amsn using git > (through git-svn), so that you may try it out before making any > decision. You could then point people to it when you need to hold > their changes waiting for a release. Anyway it's your call ;) > 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... 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... 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. 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. KaKaRoTo > -- > 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
