Re: PEAR development release

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. > 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. Any approved feature/change should go to MAIN, we can't manage 3 branches, it's a mess. > 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. 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. -- Tomas V.V.Cox mailto:cox@idecnet.com