Re: granting temporary permission for releasing packages that need a

Greg Beaver wrote:

Hi, It's been an unfortunate problem recently that sometimes lead developers don't have the time to do a new release, and so a buggy release sits out there for ages. Nobody can change the lead developer's time frame, and I don't think that's a solution. The solution is to set up a system where certain top-level PEAR folks who work on the core can run PEAR_PackageFileManager against the cvs of a package, and do a new release. Is there any interest in such a system? It would not be hard to code a short web-based script for pear.php.net admins that would accept a package name, a short changelog to use as a release information, and use the existing package.xml to create a new one and do a release. Greg

The only problems I can forsee with such a system are these: 1) What if there things that are incomplete? I assume you mean to run it on the current CVS version? 2) The last thing most developers probably write, is package.xml, therefore any cvs version is most likely out of date. I think a better solution would be the ability to change the status of said package back to beta or alpha, if it is marked as stable. - Davey