Re: PEAR development release

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. I'd like to see these committed to a branch of cvs, and a development release of PEAR packaged up and released to test the new features and allow for both debugging and refinement without disturbing anything on HEAD. A branch is the best solution because it can easily be merged, and just as easily be dropped. Any people on vacation will not need to wade through thousands of emails in order to find the patches. It's all around a better solution than the current holding pattern. I'd like to call the branch PEAR-1.3-devel, unless there is a better idea. I'll wait to the end of the week before doing anything, but if there is no negative reaction, I'll take that as an OK, since it won't disturb HEAD or PHP_4_3 branches at all. Regards, Greg

huge +1 on this. There is absolutely *no* harm in doing this. PEAR commands already built in preferred_state option will stop people unwittingly installing it, anyone who does want to test this stuff (like me) can do so easily, and as it doesn't affect anything that it currently stable, I will be astounded if *anybody* gives this anything other than a +1 - Davey