[Cosmo-dev] Re: Testing checkpoint for Cosmo 0.7
Mikeal Rogers
mikeal at osafoundation.org
Thu Jul 5 13:59:19 PDT 2007
Yeah, I didn't realize how many of those were rebranding. After
looking a bit more closely there are some P2 bugs we need fixed too.
P1
9692 br at osafoundation.org Simply Double clicking in IE7
yields error
9693 travis at osafoundation.org Modification on recurring event
9698 br at osafoundation.org IE 7 Remove broken
9699 mde at osafoundation.org Entering quotes into create
note field creates problem in...
9715 travis at osafoundation.org Cacheing of Atom content not
working properly in Firefox
9727 br at osafoundation.org 'just this event' update on
the recurrence dialog does no...
P2 ( None of these seem like P2 bugs, they sound more like P1 bugs )
7638 br at osafoundation.org Users are locked out of
editing a Collection if another C...
8158 mde at osafoundation.org IE 7 Unable to create events
on all of canvas except the ...
8350 adam at osafoundation.org Windows IE 6: app freezes when
adding an event.
8880 travis at osafoundation.org Unresponsive script error when
loading large collections ...
-Mikeal
On Jul 5, 2007, at 1:49 PM, Sheila Mooney wrote:
> What about if we didn't think of this as a dogfooding checkpoint
> but simply a testing checkpoint - bugs that prevent a full manual
> test of all the functionality. In this case, do we need to have all
> the branding items fixed? This list is mostly branding item ie:
> having the right link when you click on the help menu.
>
> On Jul 5, 2007, at 1:35 PM, Mikeal Rogers wrote:
>
>> I would say all the current P1 bugs that are assigned to
>> developers would need to be fixed before we would point dogfooders
>> at qacosmo.
>>
>> http://tinyurl.com/36d4vh
>>
>> I think more frequent bug councils are a great idea.
>>
>> Our current bug council is on Friday, should we do another one on
>> Wednesday?
>>
>> -Mikeal
>>
>> On Jul 5, 2007, at 12:11 PM, Sheila Mooney wrote:
>>
>>> Mikeal,
>>>
>>> I was supposed to get this email out earlier in the week. During
>>> the Preview meeting on Monday we discussed crafting some kind of
>>> milestone goal around getting to a version of Cosmo 0.7 that we
>>> could point testers to. This is different from a dogfoodable
>>> checkpoint, it really just means that we can have people testing
>>> the round trip features between Cosmo and the Desktop. We are not
>>> intending on updating hub.chandlerproject.org and would simply
>>> point people to qacosmo understanding that data gets wiped and
>>> the build gets updated frequently. We feel that identifying and
>>> getting to this kind of a milestone will better help us take
>>> advantage of additional testing resources.
>>>
>>> We could define this checkpoint as fixing the blockers that would
>>> prevent a full manual test. It's my understanding that there are
>>> a number of such bugs. If there are 2 many we could explore doing
>>> this in stages ie: calendar vs dashboard. Probably the first step
>>> is to get the list of problems and go from there.
>>>
>>> Questions for you...
>>>
>>> + Could you identify this list of blockers so we can have the
>>> developers working on these.
>>> + We were going to propose more frequent bug councils ie: twice a
>>> week and wanted to get your feedback on that.
>>>
>>> Thanks,
>>> Sheila
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070705/4c59e978/attachment.html
More information about the cosmo-dev
mailing list