Re: [PHP-PEAR] RFC on merge of PHPLib and Pear

[email protected] (Ulf Wendel) Thu, 08 Mar 2001 20:23:25 +0100
Newsgroups php.pear
Message-ID <[email protected]>

"Jeffrey A. Stuart" wrote:
> 
> > -----Original Message-----
> > From: Paul Meagher [mailto:[email protected]]
> > Sent: Wednesday, March 07, 2001 12:42 PM
> > To: [email protected]
> > Subject: Re: [PHP-PEAR] RFC on merge of PHPLib and Pear
> >
> >
> >
> [...my message deleted...]
> > The thought of creating a pre-pear staging area on sourceforge had occured
> > to me as well.   I'm in favor of a process that doesn't involve me having
> > to be "blessed"  by the PHP Group before I can contribute alpha level code.
> > I think blessing code (i.e., thorough code review by leading PEAR
> > contributors/commentators - Chuck, Jon, Stig, etc???) that ultimately goes
> > into PEAR is a good idea, however.
> >
> > Regards,
> > Paul
> 
> ok... here's what I'm gonna do... :)  I'm going to create a SF project for the
> initial work... Once that's done, we can see what all can/will get moved
> over...

I'm not really happy with a "pre-pear" repository. This would mean that
for all time packages that get developed by more than one person start
in another CVS but the PEAR repository :/ which complicates
contributions and stops people helping.

Rember the cool book of Tobias (Ratschiller) and Till (Gerken) and their
chapter on the project layout. They suggest a development, a staging and
a life server. I'm afraid we will not get this on php.net. At PHPLib we
used a release conzept plus a dev and a life CVS. Releases will not work
for PEAR as no one has the time to prepare releases. 

But we might consider a directory Experimental/ in the (life) CVS we
have plus a README "This is experimental, no warranty at all, no docs,
sorry..". Within the directory we use the planned directory structure. 

Ulf