Re: PEAR_ErrorStack Quality
| From: | Stefan Neufeind, PEAR | Date: | Sun, 04 Jul 2004 09:02:02 +0000 |
| Subject: | Re: PEAR_ErrorStack Quality | ||
| References: | 1 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-425@lists.php.net to get a copy of this message | ||
Davey wrote:
Firstly, I would like to point out, that putting "Alpha" code inside a package marked as "stable" should be a no-no. The entire package should be marked at the state of its lowest common denominator. (Perhaps we need an RFC on this? :)I don't remember if there is anything in the docs yet, however I'm sure this was commonly agreed upon already in the discussions. Imho you're right ... we can't run stable with alpha-parts in it (results might vary depending on the alpha-package).
Secondly, I think that the quality of PEAR_ErrorStack is suffering because Greg is forced to wait on release of the main PEAR package to release PEAR_ErrorStack. (Don't take this badly Greg, even the current code is awesome! :) I would like to propose that we seperate PEAR_ErrorStack in to its own package. We can then either have it as a dependency for PEAR (bad IMO) or just make it part of the default install. I understand we're removing all non-essential packages from the bundle, but in this case I would make an exception.Since this would also allow for PEAR_ErrorStack to be updated separately etc. you mean? Might be an idea - only problem I see is that PEAR_Error is part of the main PEAR-package and it's one of the essential parts, so it's in the core.
Is it possible for the PEAR package to include the latest PEAR_ErrorStack files when release, and then have it as a seperate package also? the former would just overwrite the latter, but any new releases of PEAR_ErrorStack would then overwrite the PEAR files - or does the installer forbid this?I don't think that it's possible for a package to contain another package. But you could have it separately - where's the problem? And for distribution purpose (packages bundled with PHP) you could still bundle PEAR_ErrorStack as well, since it would then be a vital component for PEAR imho.
I think its *essential* to developers and users that PEAR_ErrorStack always be available, I also think that its essential to the package that it have its own release cycle.You might be right that separate release-cycles might be a good idea. Makes improving the ErrorStack independently more easy - though it surely hasn't got any bugs left due to Greg's extensive unit-tests :-) Regards, Stefan