Re: Validate_HU - don't do releases unless you commit the changes to cvs.

On Wed, Feb 4, 2009 at 5:06 PM, Daniel O'Connor <daniel.oconnor@gmail.com>wrote: > Zoltan, Tibor, > I noticed someone just did 2x releases of Validate_HU in the past two days. > There are no corresponding changes in CVS ( > http://cvs.php.net/viewvc.cgi/pear/Validate/) > > > The last time I emailed you, it was about getting the package into CVS. You > didn't answer, so I put it into CVS after 3 weeks. > > If you *don't know how to or don't have cvs access, talk to us!* We'll sort > it out - just whatever you do, *commit changes to cvs* before you do a > release! > > If you don't do that, and the package breaks, you'll cause one hell of a > headache when we try to sort it out. > > > If I haven't heard from either of you in the next few days, I'll pull the > releases until the changes get into CVS. Hi Daniel, As far as I can tell, there is nothing in PEAR coding standards or manual anywhere saying a package must use CVS, or any source control for that matter. For example, many packages choose not to cvs.php.net for source control. (If I am wrong here, please disregard this message). The fact is the new release adds new features / fixes bugs - why pull it because your opinion is that the code should be in cvs.php.net? If it does break something, a bug report can be filed and the developers can fix it. Having it in CVS won't prevent the bug from happening. Don't get me wrong--I am definitely in favor of requiring packages to be under source control, but I think until there is an RFC passed saying packages are required to live in source control, I don't think you should pull a release because it isn't. Also, Validate_IT and Validate_RU don't appear to be under CVS. Regards, --Matthew