It appears we can't expect any more improvements on the Google code site to support the move, thus we might as well get it started.
As I understand it, the move will redirect most things to github, hopefully also deep-linking for issues. Not sure how well this works, can't try it out without actually doing the move. The repository is expected to keep working for a while. It's good that you can keep getting Vim, but it will soon be an outdated version. The only solution I see now is to check in a change to the Makefile to give an error and a URL where to find instructions to move to github. This needs to be done before it goes read-only on August 25. Roughly the steps would be: 1. Stop making changes: "freeze" 2. Use the move tool on Google code to move the Vim project to github. Check that it completely worked. 3. Clean up the repository. 4. "unfreeze", continue committing patches, editing issues, etc. 5. Tell everybody to start using github, add a message on Google code that the site is deprecated, any change will be discarded. Patches will go to github only. 6. After checking that it works, set the Google code site to the "project moved" state. Mercurial keeps working still, but gets the older version. 7. Check in a change to the Mercurial repository to break the build. This must be done before August 25. 8. Repair any damage, update broken links, etc. For the second step, I only have sketchy instructions. I really need step-by-step instructions to make sure we end up with the right repository. Markus, can you do this and try it out? I do think we first need to use the export tool, so that all deep linking (for as far as that works) will be put into place. But we could wipe the repository on github and redo the import with a cleaned up repository. I would also like to put up a page with clear instructions on how to switch from Mercurial to git. Should be a simple one for when there are no local changes, a slightly more complicated one for when one has made local modifications. The move should include going from Mercurial to git, but there can also be a separate part for how to keep using Mercurial and sync from github. Who can work on this? -- You were lucky. We lived for three months in a brown paper bag in a septic tank. We used to have to get up at six o'clock in the morning, clean the bag, eat a crust of stale bread, go to work down mill for fourteen hours a day week in-week out. When we got home, our Dad would thrash us to sleep with his belt! /// Bram Moolenaar -- [email protected] -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
