vcs:svnfaq:firefighting

This is an old revision of the document!


Moving to SVN: FireFighting

As we probably have to switch VCS sometime in the future we need to document all cvs->svn fires that break out so we can be better prepared next time.

This page should contain all known fires - so please update when you start seeing the smoke.

It would also be appreciate if you can assign your name to fires to avoid duplicated work.

Be sure to read svnfaq too :)

General fires

  • The daily “changelog” script needs to be updated to use SVN

bugs.php.net

  • Uses a local copy of CVSROOT/passwd for authentication. Needs to use the API on master.

docs.php.net

  • Uses CVS checkouts for bunch of things, need to be updated to use SVN checkouts

pear.php.net

  • General changes to the PEAR manual to reflect svn and svn.php.net rather than cvs.php.net

pecl.php.net

  • Minor changes to http://pecl.php.net/support.php to reflect SVN rather than CVS on links “PECL/PHP Coding Standards” & “PHP5/ZendEngine 2 Object internals”

rsync.php.net

  • Uses cvsup to update everything rsyncable (cvsup needs fixing to point to svn?) (Derick?)
  • phpdoc is built from cvs checkouts (needs to be 'generalized' to use “phpdoc-build” user/group) (Derick?)

snaps.php.net

  • Needs to use SVN for checkouts (derick)

oti1.php.net

  • This windows box (chm builder) needs to be upgraded to use SVN rather then CVS

Websites

http://php.net

  • http://php.net/cvs-php needs to be updated to talk about SVN (sstratton)
    • Intent is to create svn-php and redirect cvs-php
  • http://php.net/anoncvs needs to be updated to talk about SVN (mgdm)
    • actually it would be better to rename it to anonsvn and redirect anoncvs to that
vcs/svnfaq/firefighting.1247284332.txt.gz · Last modified: 2017/09/22 13:28 (external edit)