[wp-hackers] WordPress 2.0.3 Tuneup Plugin

[Computer Guru]

I can imagine the issues involved in releasing another build, but like I
said earlier, this isn't a very big bug, and I guess there is no hurry to
get it fixed. ATM anyone that knows about the bug knows about Mark's
plug-in, so it's not as big of an issue as it seems.

But this can be seen as a good thing, I mean, we obviously have serious
issues in testing WP, and this brings them to light. This time it's a simple
annoyance bug, next time it might not be. I'm really guilty here, I've been
running SVN for the longest time, and hacking the hell out of WP, but never
reporting back, but I've resolved to change :D

There are a lot of people running the SVN as you said, but the trick is to
get them to report back. Post on the dev blog, make it clear that WP is a
community project that needs the help of everyone involved. I have been
contacted by many people that found WP bugs, but they didn't realize it.
Most geek bloggers enjoy the bragging rights that come with SVN, but aren't
comfortable with mailing lists. To be honest, WP support forums aren't the
easiest way to report bugs. Make it _easier_ for John Q. Public who happens
to run SVN or RC to report back, and that might make all the difference.

Computer Guru
NeoSmart Technologies
http://neosmart.net/blog/


-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Matt Mullenweg
Sent: Sunday, June 04, 2006 7:32 AM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] WordPress 2.0.3 Tuneup Plugin

Stefano wrote:
> problem = bugs then it's a buggy version.... and this happened just 
> cause from beta to release ther was only few hours.

The code with the problems has been in testing for weeks, possibly as long
as a month. The code was new to the 2.0 branch, but the bugs were identical
in the 2.1 SVN, which supposedly has more testers. (A surprising number of
people run off trunk, including all of the active contributers I know of.
However those folks, including me, seem to miss or ignore bugs sometimes.)

The lack of people testing SVN is part of the reason I've been encouraging
frequent syncs of SVN to the WP.com live site, because that has so many
people using it even obscure bugs get reported very quickly.

However because of Donncha's wedding and honeymoon, we hadn't synced the
codebase in about a month (before nonces were added) so these seemingly
obvious things weren't caught.

Testing is not sexy! We've tried writing guides, mailing lists, nightly
builds, short betas, really long betas, nothing that has been suggested
hasn't been tried. At the end of the day, more people using every little
part of the system every day is the only way that has consistently kept
development pretty stable. On the downside, it's a lot more work to
constantly sync and it often makes WP.com less stable.

That was a long-winded way of saying I've finally found something that I
think works, but has some drawbacks. The same thing could be replicated on a
smaller scale by any dedicated developer who hosts blogs for 5-20 friends.

> If you think that having 2 rlease in one week sounds good.. ok.. I 
> dounbt it is, just for the image of the software

Very true, we can roll up these and any other bug / security fixes that come
up for another release in the 2.0 series in about a month or so.

(Sorry to respond just to your email, this was something a few people have
brought up in the thread.)

--
Matt Mullenweg
  http://photomatt.net | http://wordpress.org http://automattic.com |
http://akismet.com _______________________________________________
wp-hackers mailing list
wp-hackers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers