Git migration: next step

[Arkadiusz Miśkiewicz]

On Tuesday 03 of April 2012, Kacper Kornet wrote:
> 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

Is cvsadmin job for git described anywhere?

How I (as user) can change my ssh key?

"admin defined command" - 404

> http://www.pld-linux.org/dokuwiki/howto-git

Are auto- tags restricted for pld-builders only? (should be).

How workflow with DEVEL or APACHE_2_2 and such branches should look like? (aka 
are there any things different from cvs)

> So there are following questions:
> 
> A. Should PLD move to git with the similar setup?

I like trying new things and have nothing against git.

> B. Is there anything more that should be done before D day?

We have few scripts in CVSROOT (restricting access, cia bot notification, 
commit log notification, cdg, namecheck, filter tags,...). Are these scripts 
ported to git version of repository?

> C. When should the migration take place?

When you and someone else have bunch of free time to do all of it :-) I could 
find some time over one of the weekends but I want "big move" to happen first.

> Assuming that the migration to git would take place it could go
> according to the following plan:

> 2. Push converted repositories from gitolite setup on carme to
>    git.pld-linux.org

I would go for converting from current cvs from scratch (especially things are 
modified on cvs server side sometimes). How long such conversion takes?

> 3. Setup git-daemon and gitweb access

gitweb == or != cgit nowdays?

> 6. Setup mailing list for git commits

Will be the same as current list.

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/