[devel] Perl switching to git

[Alexey Tourbin <at@altlinux.ru>]

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

----- Forwarded message from Rafael Garcia-Suarez <rgarciasuarez@gmail> -----

Date: Thu, 6 Mar 2008 13:47:22 +0100
From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail>
Subject: Switching to Git
To: "Perl 5 Porters" <perl5-porters@perl>
Message-ID: <b77c1dce0803060447m12cf2ed9v2dbe17ed59e6073@mail.gmail.com>

Thanks to Sam Vilain's hard work, we are now able to switch to git.

So we'll switch!

The hosting details are being sorted out. The things that we want to have are:

* public repository cloneable via git protocol (optionally http protocol too)
* writable via ssh
* browseable on-line via gitweb
* maybe a cvs interface (readonly) via git-cvsserver ? I'm thinking
about the VMS people here mostly. Or would rsync be better ?
* interfacing the commits to the major branches to perl5-changes@.

Please add your suggestions to that list.

We are going to give more commit bits than previously. I'm notably
thinking about dual-life module maintainers. They should be able to push
their changes directly in a branch of their choice, that the pumpkings
would later merge to blead/maint-*. (Alternatively the pumpkings could
pull changes too, but why make things complex.)

I'll make the proper official announcements once we start using the new
repository; I'm thinking for now about use.perl, perlbuzz and the
official TPF blog. (Plus of course the git mailing list.)

Also, the APC is going to be obsolete. Andreas' magic tool too (see
git-bisect(1) for why), sorry Andreas :) I however would like to thank
ActiveState for providing P5P with such a nice version control system
and support for all those years.

----- End forwarded message -----

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]