RE: [PEAR-DEV] granting temporary permission for releasing packages that need a new release

> From: Pierre-Alain Joye [mailto:paj@pearfr.org] > Sent: Thursday, August 07, 2003 10:33 AM > On Thu, 7 Aug 2003 10:31:01 +0200 > Martin Jansen <mj@php.net> wrote: > > > I'm strongly against this. The lead developers of a package are > > responsible for their code and its release cycle. Having some other > > people that may roll new releases as well, will result in a big mess. > > > > Remember: PEAR does only provide the infrastructure, but every package > > is some sort of independent sub-project. > > Fully agreed here. I don't full agree here. PEAR wants to leave the responsibilities in terms of decision making etc with the lead developer. This is the model we offer and this is the model we should pursue in the future. However we also claim to provide high quality packages to our user base. If open bug reports linger, if fixes to known issues are committed to CVS but no new releases are made then we have a problem. Therefore there must be sort of an implicit contract, that the sovereignty in decision making requires that the developer also maintain his package properly. For now I would like to keep the definition of "properly" a soft one, which is decided upon on a case by case basis. Regards, Lukas