+1 Looking forward to being able to have feature branches
Rob On 12/09/2014 10:46, "Andy Seaborne" <[email protected]> wrote: >This is a VOTE on moving the main Jena codebase from subversion to git. > > [ ] +1 Approve the migration > [ ] 0 Don't care > [ ] -1 Don't migrate, because ... > >This vote will be open to at least the end of > > Thursday 18th September (UTC). > >(for additional discussion email, please remove the [VOTE] label in the >subject line) > > Andy > > >* Current Situation > >The master copy of out codebase is in subversion: > >https://svn.apache.org/repos/asf/jena/ > >which is mirrored to > >https://github.com/apache/jena/ > >and the "octotree" github repo browser works nicely. > >(you can see the Apache setup at > http://git.apache.org/jena.git/ >but these areas are not very informing) > >** What will move > >.../repos/asf/jena/trunk >.../repos/asf/jena/branches >.../repos/asf/jena/tags > >and it will look like the current mirror: > >https://github.com/apache/jena/ > >We'll probably want to cleanup afterwards - there are old, deleted >branches still showing at github. > >Mirroring will continue; it will be from Apache-hardware-hosted git >installation. > >** What will not move (at the moment) > >The website will remain in https://svn.apache.org/repos/asf/jena/site/. > >It uses svnpubsub -- the "svn" is a clue here. > >The top level directories which are not "trunk", "branches", or "tags" >will not move in this transfer. > >Experimental/ >Import/ >Scratch/ >content-assets/ >dist/ >site/ > >We can deal with these separately. > >** Notes > >We need a separate discussion on how to manage our open development areas. > >We can have more than one git repo. Some projects have many but >releasing out of many repos is extra work. > >dist/ needs sorting out but it's small and history isn't important. > > Andy
