Re: An alternate view of PEAR QA

From: Date: Sun, 18 Jan 2004 22:26:33 +0000
Subject: Re: An alternate view of PEAR QA
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-369@lists.php.net to get a copy of this message
Jon Parise <jon@php.net> wrote: > To that end, the QA team's job starts just after a package release is > submitted by a developer. The release is marked as "pending approval > by QA" and won't become a public release until the QA team blesses it. > The QA team has the ability to fail the release, essentially sending > it back to the developers for improvement. This is very fine, but is based on the assumption that we'll have a large QA team that can act fast. Based on the current number of releases, this would probably hamper PEAR growth. I'd hate to get into a situation where a maintainer would have to wait a month before his/her package is accepted. Of course, there could be a PEPr-like system which would set a one-week limit and if there was at least one positive vote, it would pass. If no one votes, the system would send hourly reminders to the QA core group (individual email addresses, of course, not the list) :-D > Developers will be able to mark special "checkpoint" releases that are > sent directly to the QA team for testing and feedback. These releases > will never become public. I don't like this. QA shouldn't take over the function of the pear-dev list. We don't have an unlimited amount of time at our disposal, but we generally read pear-dev and pear-cvs, which should sufficiently answer these issues. Of course, if someone has a specific question, it can be addressed to pear-qa, and should then be answered promptly. > Each package's "QA History" will be publicly available via the pearweb > interface. Good idea. > The QA process will be responsible for validating a package's quality > based on: > > - Its ability to pass its tests. If the QA team finds the tests' > coverage lacking, they may submit new tests to the developer for > the inclusion in the package. LOL! I'd love to have someone do that for my packages. If someone out there has time, it would be a great thing. However, don't count on QA for writing those things -- that's up to the package devs and volunteers on pear-dev. > - Its adherence to the established coding standards. > - Its backward compatibility. > - The quality of its documentation. Why not create a PEPr-like system for documenting these things for each release? The developer would check all boxes that apply (for example, check the box if unit tests are missing, etc.). > This proposed system aims to prevent "bad" packages from ever being > released into the wild. Unfortunately, mistakes do happen, and we'll > probably have to adopt most of Lukas' proposals [1] to deal with those > kinds of situations when they occur. But what about the dev releases? It would be very sad (and make a lot of devs mad) if dev releases couldn't be made (I'm referring to all releases with a status below "stable"). Speaking of which, it would be possible to apply your approval idea to stable packages, allowing all packages below that to pass through unhindered. This would prevent incidents like Console_Getopts a little while back. Klaus

« previous php.pear.qa (#369) next »