Re: [pypy-dev] Migration to mercurial
On 14/12/10 00:02, Antonio Cuni wrote: Hi all, finally, it's happening :-). Thanks to Ronny's work, we are going to complete the migration to mercurial very soon. so, the migration is done! The svn repo is readonly, and from now the official pypy repo is this one: http://bitbucket.org/pypy/pypy There are still some rough edges to fix on buildbot, but for the rest everything seems to work fine. I would like to thank everyone who was involved in the migration, in particular Ronny who did most of the dirty work :-) ciao, Anto ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
[pypy-dev] Migration to mercurial
Hi all, finally, it's happening :-). Thanks to Ronny's work, we are going to complete the migration to mercurial very soon. The pypy buildbot is already configured to pull from the bitbucket repository: http://bitbucket.org/pypy/pypy I have tried to run a test build, and it seems to work ok. We will see tomorrow morning how the nightly runs went. If everything goes right, tomorrow we will declare the hg repo as the official one: the svn repo will be made read-only (as soon as armin does it :-)), the mercurial one will be synchronized to include the latest svn commits, and from that point everyone should start to commit to mercurial. If you don't have write access to the bitbucket repo, please ask me or anyone else who is an admin. A note for people working on active branches: before you can work on those, you need to perform two simple manual steps, as detailed in this howto: http://codespeak.net/svn/pypy/extradoc/planning/hg-migration/active-branches-howto.txt ciao, Anto ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Re: [pypy-dev] Migration to mercurial
2010/12/13 Antonio Cuni anto.c...@gmail.com: Hi all, finally, it's happening :-). Thanks to Ronny's work, we are going to complete the migration to mercurial very soon. Excellent! Thanks for your work. The pypy buildbot is already configured to pull from the bitbucket repository: http://bitbucket.org/pypy/pypy I have tried to run a test build, and it seems to work ok. We will see tomorrow morning how the nightly runs went. If everything goes right, tomorrow we will declare the hg repo as the official one: the svn repo will be made read-only (as soon as armin does it :-)), the mercurial one will be synchronized to include the latest svn commits, and from that point everyone should start to commit to mercurial. If you don't have write access to the bitbucket repo, please ask me or anyone else who is an admin. A note for people working on active branches: before you can work on those, you need to perform two simple manual steps, as detailed in this howto: http://codespeak.net/svn/pypy/extradoc/planning/hg-migration/active-branches-howto.txt What will be happening to the other repos? ie. extradoc -- Regards, Benjamin ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Re: [pypy-dev] Migration to mercurial
Antonio Cuni anto.cuni at gmail.com writes: Hi all, finally, it's happening . Thanks to Ronny's work, we are going to complete the migration to mercurial very soon. +1 Cool. Providing binaries through bitbucket.org/pypy/pypy/downloads would be nice too. Are the bugtracking/code review facilities of bitbucket going to be used too? Or is the current https://codespeak.net/issue/pypy-dev/ here to stay? ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Re: [pypy-dev] Migration to mercurial
On Tue, Dec 14, 2010 at 9:24 AM, Seung Soo, sungs...@gmail.com wrote: Antonio Cuni anto.cuni at gmail.com writes: Hi all, finally, it's happening . Thanks to Ronny's work, we are going to complete the migration to mercurial very soon. +1 Cool. Providing binaries through bitbucket.org/pypy/pypy/downloads would be nice too. Are the bugtracking/code review facilities of bitbucket going to be used too? Or is the current https://codespeak.net/issue/pypy-dev/ here to stay? All of this will happen, it's just a one-by-one process (since they don't depend on each other). Don't worry, we'll get there :) ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
[pypy-dev] Migration to mercurial
Hi all, as some of you might have noticed by watching the IRC channel, we are finally migrating to mercurial. The actual conversion of the repository will happen at some point during next week (or maybe the week after). One issue that we have to care about is how to convert the author names: in the current svn repository each author is simply indicated by its codespeak username, while with mercurial this is no longer possible as there is no longer a centralized server where everyone has an account. In mercurial an author is just a string, but the standard way is put both the real name and a valid email address to uniquely identify the author. This is exploited by websites like e.g. bitbucket to link the author of the commit to the bitbucket user. For doing the conversion, we will use the following usermap: http://codespeak.net/svn/pypy/extradoc/planning/hg-migration/usermap.txt By default, we map each username to its real name, as found in the /etc/passwd file on codespeak.net. Because of the reasons I explained above, I strongly recommend everyone to put its email address there, so that it will be there in the final mercurial repository. If for any reason you don't want your real name to be in the mercurial repository, please kill the corresponding line in the file. Note that it won't be possible to change the info after the conversion has been made. ciao, Anto ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
