On Mar 12, 2012, at 10:59 AM, Abdelrazak Younes wrote: > The main repo would be automatically synchronized (only the 2.0 and > 2.1 branches); either via a git hook or a cron script at server side. > The cron idea is better if only we had some automatic regression > testing in place. Then only those commits that passes regression on > the cooking repo would be pushed to the main repo.
Would it be possible to have the main repo also synchronized with the existing SVN? git-svn can transparently push right to an SVN repository. That would prevent a lot of things from breaking. For example, I've been keeping a mirror of SVN on Launchpad that I use for development, testing, and (hopefully) daily builds. Retooling this mirror to pull from git would require re-importing the whole thing (a multi-day affair). If there is any way to keep our current SVN branch active with the "canonical" developer sources, that would be a wonderful thing. (Even if most of the development is happening in git.) Cheers, Rob
