RE: [PEAR-DEV] commiting bug fixes to other peoples packages (was RE: [PEAR-DEV] #25060 [NEW]: Math_Integer/Integer/gmp.php uses raisError () instead
of raiseError())

From: Date: Wed, 13 Aug 2003 09:58:19 +0000
Subject: RE: [PEAR-DEV] commiting bug fixes to other peoples packages (was RE: [PEAR-DEV] #25060 [NEW]: Math_Integer/Integer/gmp.php uses raisError () instead
of raiseError())
Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-19657@lists.php.net to get a copy of this message
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. 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. Arnaud. > I applaud your recent efforts to eliminate bugs in PEAR packages. > However currently we have no regulations dealing with when > other people > are allowed to commit fixes to packages that they are not responsible > for. Actually currently there is only the regulation that package > developers are solely responsible. > > Don't get me wrong. I am in favour of adding regulations that > will allow > people to commit those bugs fixes. However this will only be done if > developers are unreachable for a longer period of time (certainly more > than 2 weeks) and it will not be a decision up to a single person. > > I think pear group should be responsible for this for now. In the long > terms I would rather have pear qa (once this group of people > are off and > running) be the group to decide on this.

« previous php.pear.dev (#19657) next »