The ASF has already set up "official" support for Git for their projects. These technical details have already been worked out. There are MANY other projects using Git already (around 1/3 I believe).
On Thu, Oct 10, 2013 at 11:04 AM, Jörg Schaible <joerg.schai...@scalaris.com> wrote: > James Carman wrote: > >> All, >> >> We have had some great discussions about moving our SCM to Git. I >> think it's time to put it to a vote. So, here we go: >> >> +1 - yes, move to Git >> -1 - no, do not move to Git >> >> The vote will be left open for 72 hours. Go! >> >> James > > > -1 > > We have to ensure before that our tooling works with Git and that we stay > compliant to ASF rules: > > - Release from a Git branch (if we start increasing major versions more > frequently, we will have soon the requirement for maintenance releases). > AFAICS there are still problems for Maven. > - Someone raised the question about the shared stuff like site ... is that > solved? > - Which Git server has the master? At Apache? At Github? If Github, legal > consequences? If Apache, automated sync with Github? > > No objection on the switch in general though. > > Cheers, > Jörg > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
