WIP 20051212

Daryl was really ill today. Get well friend!

Charles Fenwick and Mark Swan continue to both make very significant contributions to confirm Flock bugs are valid and verify bugs are fixed. The projects success will be their success.

It is awesome having Vera as a full time Flocker, and in the office. She has wonderful energy and experience to share.

Sunday and today, I spent my time:

  • Bugs. I viewed over 300 bug emails, and 103 of those bugs have been updated since 2005-12-11, many by me.
  • I continued to mentor Jake Dahn in basic white box QA. He has updated 11 bugs since Sunday. Some of them complex! He is a learning quickly, and almost has the beast of Bugzilla in his control.
  • I cleanup up at least two wiki spam attacks, hopefully Gandalf can reduce this issue (bug).
  • I have cleaned Robin’s bugs very thoroughly, so no excuses from him about managing his bugs.
  • Both Adblock and Grease Monkey on Extend work again, big thanks to Jake and Manish. 
  • Confirmed status of Bart’s must have list in bugzilla.

Tasks for Tuesday:

  • Work with Termie, Anthony, and Chris on their respective bug lists.
  • Work with Mercurial and build instructions.
  • Confirm and verify bugs.
  • Feedback mail has grown to 2898 unread (+57 from Friday)

To not do (myself):

  • Check with Daryl on status of publishing spec.

Tasks for soon:

  • Work with community on strategy that with submitter’s permission feedback goes to community, unless submitter wants private feedback.

technorati tags: ,

One Comment

  1. Posted December 13, 2005 at 12:46 pm | Permalink

    I like this quote from Mark’s blog, “Lloyd is all things QA at Flock and he seems like a pretty good guy. I’d love to be on that project officially but I’m not sure about the hours he works. Maybe if I were a few years younger!”

    I think you are a good guy who works too much as well ;)

One Trackback

  1. By A Fool's Wisdom on April 8, 2006 at 2:43 pm

    Flockstars testing Flock

    If only a 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….

Post a Comment

Your email is never shared. Required fields are marked *

*
*