Hi again Mohammad, I was just having a conversation with Benson and started putting down the list of initial components
mayhem-parent mayhem-site mayhem-guava (formerly G-Guava) mayhem-scheduler (formerly Guartz) mayhem-spi (formerly GSPI) mayhem-test (formerly JUnice) mayhem-lifecycle (formerly Lifegycle) mayhem-configuration (formerly Rocoto) mayhem-logging (formerly sli4j) mayhem-cache (formerly Gache) mayhem-autobind so, we should have already 11 components, which is not a trivial number... maintaining a repo for each component would be not painless, WDYT? TIA! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Tue, Nov 6, 2012 at 2:02 PM, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi Mohammad! > >> >> 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. >> > > I am not a Git guru, so my PoV is maybe directed by my ignorance, but > I see less effort on 2) which, if supported by Infra, I'd be more than > glad to adopt. > > I requested Infra some details, hopefully he can collect more info soon!!! > >> so for me I would be neutral and I will help in both cases > > thanks for the support, much more than appreciated! > All the best, have a nice day! > -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
