I agree 100%.
Also, do note that all common extensions will still be direct aliases.
Meaning there should be no difference from a development perspective
(we'll still have the same set of extensions in cvs, for all practical
purposes). The only difference is that when the release manager goes
ahead and makes a new release, he'll grab the latest stable release from
PECL (which is aliased), instead of using whatever happens to be in CVS.
-Sterling
On Sun, 2003-06-08 at 12:23, Rasmus Lerdorf wrote:
> The one point on the QA issue is that nobody ever looks through all the
> PECL extensions, but we occasionally grep through all the ext/* extensions
> to make sure that an API change, or just a simple mistake that we found
> does not occur in other extensions.
>
> We need to raise the priority of PECL/* in the hearts and minds of the
> developers so that instead of just scanning ext/* we also scan PECL/*.
> Getting it out of PEAR and up to its own top-level cvs module is a start.
> It really doesn't have anything to do with PEAR and needs to be a lot
> closer to the php-dev crowd than the pear-dev crowd.
>
> -Rasmus
--
"A business that makes nothing but money is a poor kind of business."
- Henry Ford
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
