Markus Heidelberg wrote:
> Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
> >
> > OK, if there is a chance you still find some improvements for the
> > Mercurial cleanup, we better wait a bit before doing that.
> >
> > Once you have it all figured out, I hope you can send me the final
> > scripts. I wouldn't want some small mistake spoil the fun.
>
> Here are the final two scripts for HG and Git cleanup.
> The intermediate step (HG to Git conversion) you already figured out.
>
> The HG cleanup now contains the tag renaming as discussed. Do not forget
> to adapt your scripts for the new tag naming scheme using dots instead
> of dashes.
>
> I suggest to invoke each step in a copy (cp -a) of the particular base
> repository so you can easily repeat it without having to go through the
> whole chain. And for comparing the state before and after each step.
Wonderful! And just in time, I'm working on Vim today.
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
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.
Done!
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.
If someone spots a problem, please report it soon, because I plan to
start doing this today.
--
ARTHUR: Ni!
BEDEVERE: Nu!
ARTHUR: No. Ni! More like this. "Ni"!
BEDEVERE: Ni, ni, ni!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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.
