A Fool’s Wisdom

We are probably about a week away from being able to start testing extensively the next release of Flock, codename Cardinal. It’s release is planned for May.

This has allowed me to focus on feedback.

Currently, I am balancing my time between:

• Reproducing and prioritizing the bugs in the feedback that we have received and continue to receive
• Release Team and infrastructure
• Test planning, which currently means working on creating design artifacts from internal documents and discussions and filling in details. Vera helping translate makes this possible.

Since, Flock 0.5.12 (and then 0.5.13) was released, I have had the opportunity to catch up on reading a lot of the articulate, detailed feedback that you have been sending to Flock. Cardinal should reflect this, as will the releases to follow. Living up to release early, release often means that we have to focus on a few areas each release, and make smaller incremental improvements in some of the other ones.

Even for 0.5.x, we did a pretty good job responding to the feedback by fixing the product. November 16th, Daryl wrote:

I’ve created a wiki page at http://wiki.flock.com/index.php?title=Most_Annoying_Bugs at which I hope you our bleeding edgers will start to keep (and keep reasonably well pruned) a list of the most annoying issues so far in Flock. Divising some way of displaying severity of the bug based on community feedback would be neat, but I won’t pretend to tell you how to organize.

Recently, Jake Dahn went through that list to see how we did, and what was still relevant. The result is great, most issues were addressed. Maybe, it is worthwhile removing the completed ones, and doing it again?

technorati tags: flock.com, open source, community, testing, feedback, flockfeedback, flockstar, flockstars@flock.com, Jake Dahn