pear:rfc:pear2_policy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
pear:rfc:pear2_policy [2009/09/06 15:33] – Change time limit, to reserving the right to delete. saltybeaglepear:rfc:pear2_policy [2009/09/06 15:36] – update svn paths for new php svn server gauthierm
Line 11: Line 11:
   * Name:  Brett Bieber   * Name:  Brett Bieber
   * Email: saltybeagle@php.net   * Email: saltybeagle@php.net
 +  * Name: Michael Gauthier
 +  * Email: mike@silverorange.com
  
 ==== Past Author(s) Information ==== ==== Past Author(s) Information ====
Line 81: Line 83:
 Packages can be proposed either as Packages can be proposed either as
   * A completed, or relatively complete package to Pepr   * A completed, or relatively complete package to Pepr
-  * A concept, or proof-of-concept to svn.pear.php.net/PEAR2/sandbox+  * A concept, or proof-of-concept to http://svn.php.net/repository/PEAR2/sandbox
  
 For proof-of-concept packages they should For proof-of-concept packages they should
Line 88: Line 90:
   * Undergo a review by the collective (as defined in the previous section) when ready to move from alpha to beta stability   * Undergo a review by the collective (as defined in the previous section) when ready to move from alpha to beta stability
   * Once the review is complete, the package developers may request an official vote by the collective on whether the package is ready.  The vote is conducted through PEPr.  Unsuccessful packages may request a second review after fixing issues noted by the collective.   * Once the review is complete, the package developers may request an official vote by the collective on whether the package is ready.  The vote is conducted through PEPr.  Unsuccessful packages may request a second review after fixing issues noted by the collective.
-  * Successful packages may then move their development directly from svn.pear.php.net/PEAR2/alpha into svn.pear.php.net/PEAR2 using svn move+  * Successful packages may then move their development directly from http://svn.php.net/repository/PEAR2/alpha into http://svn.php.net/repository/PEAR2 using svn move
  
 ==== Packages listed in the channel ==== ==== Packages listed in the channel ====
 Only packages with a status of beta or stable are added to the public channel Only packages with a status of beta or stable are added to the public channel
  
pear/rfc/pear2_policy.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1