Re: Pearweb package validator
| From: | Davey | Date: | Tue, 01 Feb 2005 03:13:15 +0000 |
| Subject: | Re: Pearweb package validator | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2406@lists.php.net to get a copy of this message | ||
Lorenzo Alberton wrote:
Hi Greg, Greg Beaver wrote:One of the main features for users of a "stable" package is that the API is stable. Code will have bugs, its a fact of life, API stability is *more* important in this case and one of the things that QA requires of packages marked stable. If you break API, you must go to the next major version. - DaveyI think the package itself is stable, but the API may still change. Anyway, Wolfram Kriesing (being the original developer) has the last word on it, I'm just keeping his package in shape until he comes back. Regards,I'm trying to upload a tiny bugfix release of [M]DB_QueryTool. They've been marked as "stable" well before the new regulation, even if they're < 1.0.0. Should I go back to beta? Can't the package validator be a bit less strict? :)Is there a good reason it can't be version 1.0.0? If it is stable, why wait?