Re: PEAR development release

Tomas V.V.Cox wrote:

On Tuesday, August 26, 2003 20:03, Greg Beaver wrote:

Hi,

There have been a significant number of patches to the core of PEAR, both my patches, and Marshall's XML_RPC patches.

If the XML_RPC patches were good and someone reviewed them please go ahead. We could release a "beta" version with them. Btw if Marshall wants and someone has reviewed his code, I'd invite him for being the new XML_RPC maintainer.

The main problem is that XML_RPC appears to be unmaintained - I'm happy to review the code, but it would be nice if there was someone with XML_RPC expertise who could review it.

Please before commiting any new feature or visible change to php-src/pear/*, always wait for feedback. I guess you agreeded with that when you requested karma for php-src/pear. Remember that the PEAR package is the most important package, and a package that could even manage php extensions in the future. We must have a strict control over what things goes in.

I completely agree. The problem now is that there is no way to get feedback or approval easily - patches are very hard to apply on windows, and many people don't want to risk destroying the installation. I think the revert command will help solve this, as I'll be able to make a development package with an earlier version number, like say PEAR version 1.2.0.1 with state snapshot. In this way, users can simply pear upgrade PEAR to remove the development code and return to normal. I have a copy of php-src/pear in a local CVS repository at phpdoc.org, which I've only been using to keep track of my development changes. I decided to work this way because I kept accidentally committing bug fixes with changes I'd made to the original repository. With this method, I just use Winmerge to copy my changes over to the php-src/pear head selectively. Would there be any objection to publishing the URL for grabbing this development source on pear-dev, and bundling up test releases with out-of-date version numbers that can be "installed" using pear install --force? In this way, a CVS branch will be unnecessary in php-src. Regards, Greg