RE: [PEAR] Http_Upload

As written in my previous email: If you come across a problem, file a bug-report. Once you managed to fix it, please contribute your patch-file by simply attaching it to the bug-report - this way it won't get lost. Try to inform the package maintainer via email first. If they don't react within a "reasonable" (still to be defined) amount of time pear- qa is now intended to get hold of those bug-reports. You may also wish to send an email to pear-qa@lists.php.net in such a case - and be sure you'll be helped. If the package-maintainer is not available pear-qa will also do an update, issue a new release etc. whenever necessary. Hope this clarifies the situation a bit ... Regards, Stefan On 20 Feb 2004 at 8:47, Marcos Neves wrote: > I really don't want a CVS account, I try before to use it with no > sucess :( Would be nice if a package have at least two peoples with > CVS account, I really know how hard is to find a time to work on an > open project. > > I'm using PEAR classes on my projects, so when I found a bug just > report it and wait the fix is not enouth. Most time I have to patch it > as soon as possible and the least I could do is forward the patch to > the comunity. But for some packages it take too long to be updated! I > did it sometimes with DB_DataObject and Auth, and all was accepteds. > But that's happen cause Alan is in constant update, and Auth has 3 > developers. I will propose some patches to HTTP_Upload at bug system > and see what's happen. [...]