in my ex-company we used two different approaches, we were using mercurial but the same concepts apply here
1- use one repo and have branches for each component in which u make changes and then we merge that back into the main/default branch from which we make releases 2- have different repo for each component which is easier but includes maintaining more reps well in either case some effort needs to be done. for me u really don't mind using either. svn is a very powerful scm and if users are looking for git access we have git mirrors so for me I would be neutral and I will help in both cases Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 6, 2012 8:13 AM, "Eric Charles" <e...@apache.org> wrote: > > On 04/11/2012 09:14, Simone Tripodi wrote: > > Salut Olivier! > > > >> AFAIK not possible (git is poor for supporting such sparse checkout mode). > >> So we (infra folks) will have to maintain one git repo per component > >> and create a new git repo for each new component (IMHO a pain ..). > >> In some case git is probably nice but not here ! > > > > indeed, for what I can see, not all apache-commons components are > > supported in git - adding an extra step, every time a new component > > has to be created, would be not a benefit for the project. > > > >> We have very similar situation in maven projects (with some components > >> which have their own lifecycle) and we decided to not move those parts > >> to git. > > > > nice to see that another ASF community chan share a past similar experience! > > > >> But hey what is most important build a community around cool > >> code/projects or being able to use the last "à la mode" scm tool ? > > > > as I wrote in a previous message, I personally just need a SCM that > > allows me continue developing software in a comfortable way :) > > Mohammad, Eric, maybe SVN fits better for Mayhem? > > > > A git repo has to be seen like a monolithic piece of code with its full > history. If Mayhem components are aiming to have completely different > lifecycle with their own release independent, then many git repos would > be needed. > > I tend to think that 'Less is more', that 'git is now a defacto > standard', and that releasing all Mayhem components at the same time, > with the same version number (even if there is no change for some of > them) is easier for the user. > > But I am perfectly fine with SVN, except that we would create a > structure more difficult to migrate to git later on. > > Thx, Eric > > > > Thanks for the feedbacks! > > -Simo > > > > http://people.apache.org/~simonetripodi/ > > http://simonetripodi.livejournal.com/ > > http://twitter.com/simonetripodi > > http://www.99soft.org/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
