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

On Wed, Feb 4, 2009 at 9:03 PM, Joe Stump <joe@joestump.net> wrote: > > On Feb 4, 2009, at 6:17 PM, Matthew Fonda wrote: > >>> 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. >> >> 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. > > Matthew is right. Unless those releases are broken you've got no leg to > stand on to pull the releases. It should be noted that Services_Digg has > *never* been publicly available via a code repository (due to us wanting to > keep new features under wraps while we develop them). Validate_HU has been a 'problem package' for a while. A previous release was uninstallable, and despite a bug filed about it the package maintainers did nothing. After 5 months Daniel graciously picked it up and fixed the release after committing it to CVS. I can see the frustration Daniel is feeling because the package is in CVS now and this is also a pseudo-sub-package of Validate, which is in CVS. Given the problematic history of this package, I'd also like to have a bit of assurance that either a) the maintainers assure they're active and will respond promptly to problems or b) the source is kept in a vcs that PEAR QA can get to (ideally along side all the other Validate packages). I don't think pulling the release would be a kind thing to do, but I'd just like to ask the question - Do the package leads have any objections to using CVS, or even the PEAR SVN repository for maintaining the package? Are they having trouble committing to the repository or are there any other obstacles we can help with? I'm glad to see the leads are picking this package back up, and hopefully this is one less package QA has to handle - now and in the future... but let's avoid causing problems for QA and other devs in the future. If the package works, instead of pulling the release I would have QA (I'll even volunteer myself) to commit it to cvs so things are somewhat kept in sync. -- Brett Bieber