It was a pleasure to work with you people on the bug tracking day.
We may have fixed quite number of bugs and closed few features but the aim
of cleaning the bug tracker is still far as features have to be cleaned as
well. In order to keep these numbers down I suggest to spend few hours per
month together.
The aim is not to do a big Bug Squashing day with all the community, it is
more intended as dev meeting around bugs. I can list bugs and features I'd
like to close in advance and just submit the #bug to you for double check.
IMO, IRC was a good way doing it
For planification, I suggest once per month, for example the first thrusday of
each month, to be decided to match the planning of a majority of devs.
Idem for the time of the day, maybe near 4PM CET(UTC+1) to not exclude (too
much) north america. It will depend of your locations
> Hello,
>
> It was a pleasure to work with you people on the bug tracking day.
Same - you did a heck of a lot of work
> We may have fixed quite number of bugs and closed few features but the aim
> of cleaning the bug tracker is still far as features have to be cleaned as
> well. In order to keep these numbers down I suggest to spend few hours per
> month together.
>
> The aim is not to do a big Bug Squashing day with all the community, it is
> more intended as dev meeting around bugs. I can list bugs and features I'd
> like to close in advance and just submit the #bug to you for double check.
> IMO, IRC was a good way doing it
>
> For planification, I suggest once per month, for example the first thrusday of
> each month, to be decided to match the planning of a majority of devs.
> Idem for the time of the day, maybe near 4PM CET(UTC+1) to not exclude (too
> much) north america. It will depend of your locations
I've been thinking something similar. It's no good waiting 6 months
for the bugs to get back into a messy state - we need to keep on top
of it. I like the idea of monthly, and have no issues with the
proposed day of the month. Anyone else got opinions?
It was a pleasure to work with you people on the bug tracking day.
Same - you did a heck of a lot of work
We may have fixed quite number of bugs and closed few features but the
aim
of cleaning the bug tracker is still far as features have to be cleaned
as
well. In order to keep these numbers down I suggest to spend few hours
per
month together.
The aim is not to do a big Bug Squashing day with all the community, it
is
more intended as dev meeting around bugs. I can list bugs and features
I’d
like to close in advance and just submit the #bug to you for double
check.
IMO, IRC was a good way doing it
For planification, I suggest once per month, for example the first
thrusday of
each month, to be decided to match the planning of a majority of devs.
Idem for the time of the day, maybe near 4PM CET(UTC+1) to not exclude
(too
much) north america. It will depend of your locations
I’ve been thinking something similar. It’s no good waiting 6 months
for the bugs to get back into a messy state - we need to keep on top
of it. I like the idea of monthly, and have no issues with the
proposed day of the month. Anyone else got opinions?
Last Thursday doesn't work in December (Christmas) or November
(Thanksgiving). I say stick to the first Thursday as suggested - I
can't think of anything major that predictably falls at the start of
the month
···
On Wed, Nov 21, 2012 at 9:01 AM, Greg Sutcliffe wrote:
Last Thursday doesn’t work in December (Christmas) or November
(Thanksgiving). I say stick to the first Thursday as suggested - I
can’t think of anything major that predictably falls at the start of
the month
