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?
Of course at Apache. Why anywhere else? There are plenty of projects already at git.apache.org that are mirrored to GitHub. There is an established precedent. It looks Commons projects are mirrored from SVN to our Git server already. Gary 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 > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
