Re: Solution to PHP5 Exception debate (and possibly several future ones)

From: Date: Tue, 24 Aug 2004 23:09:06 +0000
Subject: Re: Solution to PHP5 Exception debate (and possibly several future ones)
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-32926@lists.php.net to get a copy of this message
As well a +1 On Tue, 24 Aug 2004 12:33:54 -0400, Greg Beaver <cellog@php.net> wrote: > Hi all, > > I think I may have a solution to the problem. > > First of all, Sergio's RFC applies to PHP5-only packages. All of my > objections so far come primarily from the concern that we would be > nailing down details before there is any actual code to verify that they > will solve problems better. > > The solution: why not assign stability levels to RFCs just as we do to > packages? > > Just because an RFC is accepted does not mean it has to suddenly become > absolutely rigid and unchanging. Assign a stability of beta to the RFC, > meaning that no package that conforms to the RFC may be a higher > stability than beta (or assign alpha for the same reason). Once there > is some experience implementing the RFC and the advantages and problems > are truly understood, it can be either upgraded to stable, or fixed and > then tested further. > > If the RFC is implemented in stable packages and a serious problem is > found, we are simply screwed. > > For any major change of this sort, it is always best to be firm but > flexible, and this is definitely an area that QA could help with > (ensuring packages conform to the changing RFC, and that they aren't > more stable than the RFC that they use). > > Any necessary changes can be voted on just the same way the original RFC > was voted on. > > Greg > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- John Downey http://www.catdevnull.net

« previous php.pear.dev (#32926) next »