Comments on: Why was WordPress 2.0 released when there were still so many known bugs? http://www.emilyrobbins.com/how-to-blog/why-was-wordpress-20-released-when-there-were-still-so-many-known-bugs-310.htm Blogging tips and tricks, theme and plugin info, blogging software reviews, and more Tue, 07 Feb 2012 07:27:12 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Robert Deaton http://www.emilyrobbins.com/how-to-blog/why-was-wordpress-20-released-when-there-were-still-so-many-known-bugs-310.htm/comment-page-1#comment-1391 Robert Deaton Wed, 04 Jan 2006 17:58:28 +0000 http://emilyrobbins.com/how-to-blog/why-was-wordpress-20-released-when-there-were-still-so-many-known-bugs-310.htm#comment-1391 All things considered, there are a few good points above. Firstoff, releasing software with known bugs is indeed a common thing, and everybody knows there will never be such a thing as bug free software, but there is a limit, and a limit to the type of bugs that can be left unfixed before release. A bug that might effect 1 out of 1,000 people is one thing, bugs like we're having with trackbacks or permalinks being broken in 2.0, however, are much worse. WordPress does not have any organized form of QA at all. There is a testers mailing list, and nightly builds, and people are just expected to keep banging at them. With a community as large as that of WordPress, this is far from optimal, and part of the problem, and is a place where the developers need to step up. There are already proposals hitting the mailing lists for a more formalized QA, <a href="http://comox.textdrive.com/pipermail/wp-hackers/2006-January/003792.html" rel="nofollow">http://comox.textdrive.com/pipermail/wp-hackers/2006-January/003792.html</a> The FeedBack link for WP.com isn't practical for regular WP blogs though, there are just too many issues that may be mistaken as bugs or that really belong in the support forum to keep a feedback link in WordPress itself, the bulk would be far too heavy. All things considered, there are a few good points above. Firstoff, releasing software with known bugs is indeed a common thing, and everybody knows there will never be such a thing as bug free software, but there is a limit, and a limit to the type of bugs that can be left unfixed before release. A bug that might effect 1 out of 1,000 people is one thing, bugs like we’re having with trackbacks or permalinks being broken in 2.0, however, are much worse.

WordPress does not have any organized form of QA at all. There is a testers mailing list, and nightly builds, and people are just expected to keep banging at them. With a community as large as that of WordPress, this is far from optimal, and part of the problem, and is a place where the developers need to step up. There are already proposals hitting the mailing lists for a more formalized QA, http://comox.textdrive.com/pipermail/wp-hackers/2006-January/003792.html

The FeedBack link for WP.com isn’t practical for regular WP blogs though, there are just too many issues that may be mistaken as bugs or that really belong in the support forum to keep a feedback link in WordPress itself, the bulk would be far too heavy.

]]>