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 On Sun, 8 Jun 2003, Sterling Hughes wrote: > What does PEAR's stability on windows 32 systems have anything to do > with it? This is an internal change. Meaning, as an end-user, you > won't see any change. The separation to PECL is purely a release > management thing. > > The move to PECL has been agreed upon multiple times. We can't have the > release manager coordinating all these different extensions at release > time. Therefore, we decide which extensions to bundle (all of current > cvs + a few PECL extensions, for example), and the release manager > bundles the last stable release. You also avoid the problem where > people can't commit alpha features to their extension, for fear a > release might be made of them (or a release is made of these alpha > features, which has happened more than once). > > Win32 is a non-issue. We're not talking about debundling anything from > a release at this point. As for QA, I suggest you look at the archives, > its been discussed multiple times (or at least, I've had this > conversation multiple times. :) > > -Sterling > > On Sat, 2003-06-07 at 19:22, Edin Kadribasic wrote: > > On 7 Jun 2003, Sterling Hughes wrote: > > > > > Hi, > > > > > > So now that the PEAR framework for bundling extensions is in place, I > > > figured I'd start a thread about moving all extensions to PECL, and then > > > selectively bundling them from PECL (perhaps maintaining physical > > > aliases as well.) > > > > -1 > > I'm strongly against this move. First of all PEAR framework for handling > > extensions is nowhere near complete. It has no support for Windows. It has > > no notion of what version of PECL package can be built with what version > > of PHP. It requires latest and the greatest GNU tools installed on the > > system which is rarely true for some commercial Unixes. > > > > If we are going to bundle most of those extensions anyway, removing them > > to PECL would directly reduce the quality of the release as most of them > > will receive very little testing. > > > > I understand the wish to make the release process more easy, but I'm > > afraid that this proposal will achieve exactly to opposite effect. It will > > certainly make maintenance of the Windows binary releases much more > > difficult. > > > > Edin > -- > "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 > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
