I think all necessary pieces of code for git migration are ready. The test setup on carme has been working for some time. So if you want to check how your favourite package would like after migration please see:
git://carme.pld-linux.org/packages/<pkg> Also some documentation has been written: http://www.pld-linux.org/dokuwiki/pld-gitolite http://www.pld-linux.org/dokuwiki/howto-git So there are following questions: A. Should PLD move to git with the similar setup? B. Is there anything more that should be done before D day? C. When should the migration take place? Assuming that the migration to git would take place it could go according to the following plan: 1. Install package pld-gitolite and git-core-slug-watch on git.pld-linux.org 2. Push converted repositories from gitolite setup on carme to git.pld-linux.org 3. Setup git-daemon and gitweb access 4. Import ssh keys of PLD developers 5. Import git versions of rpm-build-tools and pld-builder.new from https://github.com/draenog/rpm-build-tools https://github.com/draenog/pld-builder.new 6. Setup mailing list for git commits 7. Switch off RW access to cvs.pld-linux.org/rpm/packages 8. Setup src-builder 9. Update distfiles to version from branch git in cvs.pld-linux.org 10. Update packages which were changed in CVS between point 2. and 7. 11. Switch on RW access to git.pld-linux.org for all developers -- Kacper Kornet _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en