I think it'd be better to do this on a day when most people are in the office, both to allow paired problem solving and to avoid using up one of my more productive days of the week. Also, weekly feels too frequent to me: if we have to take one step back for every four forward, we should be doing something different on those "forward" days. ;-)

So if we're gonna do this, I'd suggest Thursdays before the milestone Mondays.

...Bryan

Heikki Toivonen wrote:

We'd like to introduce weekly bug bash days. The proposal is that on
Wednesdays we would put our feature work aside and concentrate on fixing
the slowly-but-surely accumulating bugs that we all would just like to
forget ;)

If you don't have any bugs (how could that be?), we'd like to see new
unit tests.

Are weekly bug days too frequent? Should the period be longer than a
day? Would some other day work better?

--
  Heikki Toivonen

------------------------------------------------------------------------

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to