An alternate view of PEAR QA

From: Date: Sun, 18 Jan 2004 22:03:02 +0000
Subject: An alternate view of PEAR QA
Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-368@lists.php.net to get a copy of this message
Here are my musings on the role of the PEAR QA team: In order to achieve the best results, quality assurance should operate on a per-release. QA members should not be concerned with development- specific systems such as CVS. Instead, their view into the package world should focus on pearweb's interface. 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. 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. Each package's "QA History" will be publicly available via the pearweb interface. 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. - Its adherence to the established coding standards. - Its backward compatibility. - The quality of its documentation. 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. This is roughly the exact same proposal that I made for the initial formation of the PEAR QA group over six months ago: http://news.php.net/article.php?group=php.pear.qa&article=21 [1] http://news.php.net/article.php?group=php.pear.qa&article=356 -- Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)

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