RE: [PEAR-DEV] commiting bug fixes to other peoples packages (was RE: [PEAR-DEV] #25060 [NEW]: Math_Integer/Integer/gmp.php use
| From: | Stefan Neufeind | Date: | Wed, 13 Aug 2003 10:39:53 +0000 |
| Subject: | RE: [PEAR-DEV] commiting bug fixes to other peoples packages (was RE: [PEAR-DEV] #25060 [NEW]: Math_Integer/Integer/gmp.php use | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19663@lists.php.net to get a copy of this message | ||
On 13 Aug 2003 at 11:58, LIMBOURG Arnaud wrote:
> I remember somebody telling me that people who have CVS should be able
> to commit things. If the maintainer don't like it, cvs is there for a
> purpose, you can always revert.
Well, I wouldn't generally agree with you in this point. If multiple
people keep submitting "junk" (take it as it is) that's far more work
than if you send diff-files via email to the maintainer. Or if he
agrees you might surely fix it yourself.
In this case the fixes were quite small so the desire for "fixing it
on the go" in CVS was there. But I can also very well understand
Pierre's points for not letting this become a "common behaviour".
It's good that people "should not" submit to CVS without prior
arranging with the package-lead. And for these rare cases in which
small fixes haven't been added for a long time or if a developer is
unavailable for a longer time as far as I understood it we might have
the "pear-group" in a not too far future.
> That said if there are patches waiting for maintainer feedback and no
> is provided for a length of time then i think it's ok to commit. There
> will be no release anyway so that won't affect people.
Yes. But you can't judge that own your own impression of the "length
of time". That's a thing the pear-group will we be there for to
coordinate.
Stefan