pear:pear2:migration

This is an old revision of the document!


Migration to PEAR2

Goal

Swap the websites (and by extension, community) so that pear2.php.net is the way PEAR is perceived, interacted with and contributed to.

How?

Two options:

  • Sudden cutover - redirect traffic to pear2.php.net; use the migration pain to inspire contributions and improved functionality.
  • Phased migration - component by component swap processes such as PEPR over to feed into pear2; co-brand the pear.php.net front page experience; end of life unsupported packages.

Phased: Timeline & Tasks

  • Kill off news from pear.php.net1); or replace it with a new pear blog2).
  • Tweak PEPR to be a new package process for pear2
  • Enable both the PEAR and pyrus installer to understand “I have migrated to another channel”
    • Kill old packages from pear.php.net. With fire. Put them in an archive channel or other location
1)
simple release of pear_index
2)
install wordpress on test.pear.php.net; update pear_index to point at new rss; and write content
pear/pear2/migration.1304378891.txt.gz · Last modified: 2017/09/22 13:28 (external edit)