Flockstars testing Flock

Flock Bug Hunting

If only I could write as fast as I think. No, writing is not the main problem. It is describing my thoughts in a concise way.

Describing incorrect behavior (symptoms) of software in a concise way is what reporting a bug is. Bug hunting is not easy.

Testing for the next release of Flock ("Cardinal") has started. Flock is lucky to have some amazing bug hunters!

People that contribute to open source projects tend to contribute in three to six week sprints. That is about all the time people can find before their full lives catch up to them. I also call it a sprint as I am always impressed by how much people achieve in the time.

At this early phase of Flock’s development, testing contribution is one of the most important and visible. It will continue to be very important. Thank you!

Lloyd Budd, Flockstars » Flockstar Spotlight: Charles Fenwick

I, Eli and Flock Testing have been incredibly fortunate to have the consistent contribution of Jake Dahn (Flockstar Spotlight)!

With Jake, the following people are currently generously volunteering their time testing Flock:

Flock Testing Alumni:

And a couple of contributors prefer to keep their identities private including toms.vaio and flock31070 .

We learn from each other. I am fortunate to work with such talented people!

technorati tags:
, , , , , , , , ,

This entry was posted in Collaborating, Flock, Open Source, QA, Testing. Bookmark the permalink.

4 Responses to Flockstars testing Flock

  1. Pingback: Jon’s SimplyTech Blog » Method for disabling Windows Genuine Validation

  2. I’ve been doing some work with Flock 0.5.x, especially finding and fixing bugs and reporting them to Jake Dahn. :) I will try out 0.7 hourlies once they become more stable.

  3. Pingback: A Fool's Wisdom » Favorites is feature complete for Cardinal

  4. Pingback: Thank the weekend Flock! at A Fool’s Wisdom

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>