Re: Quality control of PECL modules
| From: | Greg Beaver | Date: | Thu, 23 Feb 2006 05:14:12 +0000 |
| Subject: | Re: Quality control of PECL modules | ||
| References: | 1 2 3 4 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-3534@lists.php.net to get a copy of this message | ||
Wez Furlong wrote:
> Stability:
>
> We could follow the lead from the Sun folks; they make a point of
> marking up the documentation of their various APIs and tools with
> attributes defined in the
> attributes(5) man page
> (http://docs.sun.com/app/docs/doc/816-3328/6m9k8pg0c?a=view)
>
> One of these attributes is "Interface Stability", which clearly
> defines levels of stability. We could adopt this nomenclature in our
> documentation and package releases.
This is another reason to be using package.xml 2.0. It converts the
<state> tag to:
<stability>
<release>beta</release>
<api>stable</api>
</stability>
allowing you to specify the "interface stability" (I chose to call it
API stability). This allows easy definition of whether users can rely
upon their connection to the code as feature-frozen or in flux,
independent of the code stability. Not sure if this is exactly what you
mean, but it seems a good close match.
> Active Maintainer:
>
> We already track the maintainers on the pecl package pages. We
> distinguish between "lead" and "regular" developers; "leads" are
> effectively the active maintainers. I think we just need to make it
> clearer what that means.
Another reason to use package.xml 2.0 :).
The new maintainer tags allow you to specify active or not, so
historical leads can be documented as inactive lead.
Greg