Re: please do not use CVS of PEAR for anything important until REST is worked out.

On 5/5/05, bertrand Gugger <bertrand@toggg.com> wrote: > Hi Greg ! > I'm not sure to understand your message. > I assume you mean not using the pear from cvs for production ... > I will keep on testing it. > Just what should we do with the bugs/features we find if we cannot use > the bug system ? > If your stuff is unachieved, then simply don't publish it untill you are > happy about it. > That's not quite fair, bertrand. CVS is for the developer to store their changes in. Sometimes I will commit something to CVS, even though it's not done, to make sure that I don't lose changes. I also may commit if I'm going to try to refactor but I don't want to lose the changes I made so far just in case I want to revert. Basically, Greg is giving us a small courtesy here by telling us not to use PEAR's CVS because he expects it to be unstable. This is how we should always think of CVS code unless told otherwise. > > Greg Beaver wrote: > > > Hello all, > > > > I am trying to juggle several things at once in my life, and so > > development has slowed a bit. It is nearly summer, and the dormant > > PEAR developers will surface soon :). Please do not use CVS of PEAR > > or report bugs in it until I/we have a chance to get the unit tests > > working and develop a whole new set of tests for REST-based stuff. > > > > Any bugs you report will simply be fixed by these actions, and in the > > mean time, 1.4.0a11 works very well for everyday actions. > > > > Thanks, > > Greg > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Justin Patrin