Re: Re: !!! Net_SMTP v1.2.4 is broken - please remove urgently !!!

Klaus Guenther wrote:

Pierre-Alain Joye <paj@pearfr.org> wrote:

On Thu, 11 Mar 2004 14:04:36 +0100 klaus@capitalfocus.org (Klaus Guenther) wrote:

This is why QA needs karma! And please don't pretend that only a maintainer can pull a release...

I do, at least for now. But we should be allowed to remove a release.

which is what I said... QA should be able to pull (remove) a release (I didn't say roll one).

ok lets keep this thread here. pear-core is focused on infrastructure creation and therefore should not be included in qa related things. If we ever need infrastructure we can mail them :-) Anyways maybe we do need to return to the topic of coming up with a regulation of how QA should work in order to have other people also able to remove releases. I didnt think we would have to do it this often, but shockingly enough untested packages are released often. However the situation is not that dramatic since Pierre and I are online alot and I am very willing to take the blame for fixing other peoples mistakes if that improves the quality of packages. Anyways I am on the verge of becoming disgruntled, but we better not go that way. I am really starting to understand Jani more and more :-) We try to ensure quality, help developers fix their mistakes and in return people call us "pedantic", "power hungry" etc. As such it seems to me like the best course of action is the following: We offer to package developers to take over release management for them. We only do this for packages where we feel we can actually QA. This means we have to know the package and/or it needs to have good docs and/or it needs to have a test suite. All packages that do this get the QA seal of approval, which is shown on whereever possible for each given package. The developer focuses on creating a new release in CVS only and then comes to us for the actual release. We handle the release with more routine and by running the tests on the given release and then agree on making the release. This is essentially a cross breed of Jon's and my proposal. The idea would be that developers actually want us to add this seal of approval and therefore improve their docs, add tests and generally cooperate with us. Those developers that dont cooperate with us for whatever reason dont need to be annoyed by us going crazy or "abusing" our powers. For those packages we will behave just like any PEAR user. If it breaks we mail pear-dev and/or file a bug report, but we dont remove releases or any such thing. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07