For Programmers: Free Programming Magazines  


Home > Archive > PHP PEAR Questions and Answers > July 2006 > Re: [PEAR-QA] Criteria for stable release









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: [PEAR-QA] Criteria for stable release
Arnaud Limbourg

2006-07-12, 6:58 pm

Hi,

A stable package should have end-user documentation (not just API) and
provide a couple of examples. More examples, faq,e etc are also nice to
have .

it is a set of guidelines rather than an enforced rule. The most
important thing is to have end-use doc, this is what pear gets shot down
for most of the time.

Arnaud.

James Stewart wrote:
> I've had a number of users tell me they're finding XML_Feed_Parser to
> be stable in their day to day use and ask if I can move it to a stable
> release.
>
> I have a few to do items I want to deal with before that, but other
> than those I'm not sure if there is a particular process I need to
> follow to bring the package to a stable release? Does it need to be
> reviewed, or can I just mark it as stable when I'm ready? I'd like to
> get a release candidate ready within the next ten days.
>
> James.
>
> --PEAR QA Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com