Re: PEPR for PEAR2
| From: | Daniel O'Connor | Date: | Tue, 03 May 2011 10:57:27 +0000 |
| Subject: | Re: PEPR for PEAR2 | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-54262@lists.php.net to get a copy of this message | ||
>
>
> > What would we need to change about PEPR to make it be "PEPR for
> > PEAR2"?
> Implement the PEAR2 rules for new packages :)
Where exactly do those live?
http://pear.php.net/pepr/index.php?filter=finished
lists only a handful of
RFCs
Do you mean https://wiki.php.net/pear/rfc ?
https://wiki.php.net/pear/rfc/pear2_class_naming
- ratified
https://wiki.php.net/pear/rfc/pear2_standards
- expired draft
https://wiki.php.net/pear/rfc/pear2_naming_standards
- defunct
https://wiki.php.net/pear/rfc/pear2_exception_policy
ratified
https://wiki.php.net/pear/rfc/pear2_versioning_standard_revision
- draft
I'm more than happy to implement changes or link to docs - I just need a bit
of clarifty on what's considered current.
> You know, having a
> non-public channel for non-approved packages and less visibility for
> non-approved ones.
>
>
> > http://pear.php.net/manual/en/developers-newmaint.php
> > Revamp of the new maintainers guide to reflect pear2 standards;
> > expectations; building / testing your package with pyrus.
> We should start a new manual/section for pear2. I'd not upgrade the old
> one.
>
> +1