Hi Mark,
thanks for starting this! Looking forward to the whole process. When Infra is about to “activate” the new GIT repo, I will take care of Policeman Jenkins and fix the remaining validation tasks. I don’t want to do this. I think your commit is fine. We now need some workflows how to merge between master/trunk and the release branches. Projects do this in different ways (cherry-picking,…). I have no preference or idea, sorry! I only know how to merge feature branches into master :) You mentioned that we should make the old svn read only. Maybe do it similar like we did during LuSolr merge: Add a final commit removing everything from trunk/branch_5x and leaving a readme.txt file in trunk and branch_5x pointing to Git. All other branches stay alive. After that we could make it read only – but it is not really needed. What do others think? Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Mark Miller [mailto:[email protected]] Sent: Saturday, January 09, 2016 10:55 PM To: java-dev <[email protected]> Subject: Moving Lucene / Solr from SVN to Git We have done almost all of the work necessary for a move and I have filed an issue with INFRA. LUCENE-6937: Migrate Lucene project from SVN to Git. https://issues.apache.org/jira/browse/LUCENE-6937 INFRA-11056: Migrate Lucene project from SVN to Git. https://issues.apache.org/jira/browse/INFRA-11056 Everyone knows about rebase and linear history right ;) - Mark -- - Mark about.me/markrmiller <http://about.me/markrmiller>
