Hi,

The stuff I wrote is not a BC break or a feature addition, so it will be 
in the next version if it is proven to be stable.  The core devs are 
working on a roadmap for future versions, there was some talk of a 1.4, 
but nothing is finalized.  Both Tomas and Pierre-Alain are temporarily 
busier than usual, so it may be a while before anything public is 
released (and we know Stig is practically gone :).

Some of the priorities include implementing the new BC stuff, making 
PECL binaries easier to distribute, and other PECL stuff.  Also the new 
revert command, making PEAR work under PHP 5, and one of the most 
important, converting pear packages to other package systems so linux 
systems can bundle PEAR packages more easily.

Regards,
Greg

Martin Jansen wrote:

> On Sun Nov 30, 2003 at 01:2517PM +0100, Stefan Neufeind wrote:
>   
> 
> >On 30 Nov 2003 at 12:57, Martin Jansen wrote:
> >
> >    
> >
> >>On Sun Nov 30, 2003 at 12:5108AM -0500, Greg Beaver wrote:
> >>      
> >>
> >>>In any case, since the code is experimental, there is plenty of time
> >>>to snipe at it and find improvements I missed.  When it stabilizes,
> >>>I'll simply merge it with the code, and we'll be in business.  The
> >>>question is whether to do that before version 2.0, 
> >>>        
> >>>
> >>What else will change in 2.0? If there are other changes as well, I
> >>suggest to not include your patch in 2.0, but to release 3.0, which
> >>contains the new installer code, relatively short afterwards.
> >>      
> >>
> >We're currently waiting for a 1.3 final and then 2.0 will be the next 
> >thing to work on - or did I miss a thing?
> >    
> >
> 
> Correct. However I was wondering if there are already some plans
> regarding version 2. If that's not the case, it is IMO safe to include
> Gregs patches then.
> 
>   
> 

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php