Re: PEAR development release

> 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. I'm for it, i'd test the new features ;) Arnaud.