[Cosmo-dev] Changes to the bug council

[Ted Leung]

Ok,

The intent here was to reduce work, not create it.   Is there  
anything else that we can do to improve/streamline the bug council  
process?

Ted

On Oct 11, 2007, at 12:33 AM, Mikeal Rogers wrote:

> I'm not sure if this works as well for QA as it does for Dev.
>
> Developers assigned to components will get a mail about relevant  
> bugs when they get logged since they are automatically assigned to  
> them, but QA doesn't.
>
> We don't have time to look at all the bugs logged, and the areas  
> are split up between different people in QA.
>
> But I'm not opposed to this policy if before you update the bugs  
> you ping QA to take a look at them and comment. Then we can all  
> look through in one big swoop.
>
> -Mikeal
>
> On Oct 10, 2007, at 11:09 PM, Brian Moseley wrote:
>
>> On 10/10/07, Ted Leung <twl at osafoundation.org> wrote:
>>
>>> Instead of meeting weekly, current bug council attendees should go
>>> through and leave any comments that they have on bugs that are of
>>> interest to them.    At a regular time (probably the existing bug
>>> council time), I will go through and assign all the bugs, taking
>>> people's comments into account.   This means the people only need to
>>> pay attention to bugs that they have a particular interest in.
>>
>> that's one more thing for me to have to remember to do, whereas
>> currently i don't have to think about bugs until i'm forced to by bug
>> council.
>>
>> it wouldn't be the end of the world, but the fewer recurring tasks i
>> have to track, the better.
>> _______________________________________________
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev