Re: Re: cvs: pearweb /include pear-database.php /include/Damblan/Log Print.php /public_html/admin package-maintainers.php

From: Date: Mon, 22 Aug 2005 16:37:11 +0000
Subject: Re: Re: cvs: pearweb /include pear-database.php /include/Damblan/Log Print.php /public_html/admin package-maintainers.php
References: 1 2 3  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-3718@lists.php.net to get a copy of this message
Martin Jansen wrote:
On Wed Aug 17, 2005 at 07:3548PM +0200, Klaus Guenther wrote:
On 8/16/2005 8:46 PM, Martin Jansen spake the following words:
mj Tue Aug 16 14:46:21 2005 EDT
 Added files:                    /pearweb/include/Damblan/Log	Print.php 
 Modified files:                 /pearweb/include	pear-database.php    /pearweb/public_html/admin	package-maintainers.php  Log:
* Added a new interface for managing package maintainers. * Added a new logging observer to Damblan which simply prints log messages to the screen. # This new approach is necessary in order to make sure that the package.xml # files always contain the same maintainership information like the # database. It is probably not as nifty as the old one, but it's a real # improvement in terms of data integrity.
     
Yes, in that sense it's an improvement, but what about us poor QA people who just want to assign someone karma to make a release?
I'm not sure about the current state, but aren't QA people able to roll releases without being a maintainer anyway? - Martin I wan talking about mangaging the maintainers' list (in case there is a new maintainer or there is a resignation).
For example Lukas wants to be off MDB maintainenance, when I upload the new package.xml I get The following log messages were generated by the update process:
     ERROR:
         o maintainer::remove: insufficient privileges
Arnaud.

« previous php.pear.core (#3718) next »