Markus Heidelberg wrote: > > Wonderful! And just in time, I'm working on Vim today. > > Then staying up late was worth it :)
And thanks for checking the plan. > > So, these are the steps to be taken: > > 1. Stop making changes: "freeze"; announce on Google code project page. > > Announce on the vim maillists. > > 2. Run ~/tmp/clean_repo.sh on the Mercurial repo. > > 3. Push to Google code. Google code will remain in this state for a week. > > 4. Delete the testing repositories on github. > > Put a note on the github site that it's under construction. > > 5. On Google code, use the export functionality to move to github. > > This will create the "Vim" repository there. > > > > This will take some time. While that's happening do this locally: > > > > 6. Change my scripts to use the new tag format: v7.4.999 > > 7. Commit a change in the Mercurial repo to break the build, pointing the > > user > > to github. Do NOT push this yet. > > 8. Convert the Mercurial repo to github. > > 9. Commit a change that undoes the build breakage. > > 10. Run the git cleanup script: ~/tmp/clean_git.sh > > In my opinion it would be a shame to start with such two workaround > commits in a repository just cleaned up. They will live there forever, > the workaround will only be used for the then old HG repository on > Google until the switch-off in January 2016. > > As far as I understood the procedure Christian uses for the HG mirror, > it doesn't matter at all whether these two commits exist in the Git > repository or not. It should be possible to apply the unbreak patch only > to the HG mirror. > > So I suggest to swap 7. and 8. and leave 9. for Christian. That's OK with me. So we have the git repository start just before the commit that changes the build. I've decided to not actually break it, it appears that an annoying message should be sufficient. For users who switch from Mercurial on Google Code to the Mercurial mirror, there would be an extra commit that doesn't exist anywhere else. I hope that will work. > > Wait for the move tool to finish, check that it looks OK, all issues have > > been > > moved. > > > > 11. Use git push --mirror to overwrite the repository at github with the > > cleaned up one. > > 12. "unfreeze", continue committing patches, editing issues, etc. on github > > 13. Tell everybody to start using github, add a message on Google code > > that the site is deprecated, any changes will be discarded. > > My patches will go to github only. > > 14. Push the change to the Mercurial repository that breaks the build. > > This must be done before August 25. > > 15. After checking that it works, set the Google code site to the > > "project moved" state. Mercurial keeps working still, but gets the > > older version, with the broken build. > > In case you didn't already have the idea: > In the broken build you might want to point to the HG mirror or to the > Vim site with documentation for switching. Yes, I started a page for that, it's not linked anywhere yet: http://www.vim.org/movetogithub.php > > Done! > > Looks good. > > > Note: steps 9 and 10 may be swapped. I think it's best to undo the > > build breakage first, so that it's immediately after the commit that > > breaks it. But I'm not 100% sure this doesn't cause a problem for the > > git cleanup. > > I guess it should not make a difference, but as I wrote, I'm not in > favor of this approach. -- TALL KNIGHT: We are now no longer the Knights Who Say Ni! ONE KNIGHT: Ni! OTHERS: Sh! ONE KNIGHT: (whispers) Sorry. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
