8,288
edits
Changes
Jump to navigation
Jump to search
Line 17:
Line 17: − + − + Line 35:
Line 35: − + + Line 44:
Line 45: +
no edit summary
Title: Testing Session
Title: Testing Session
*Time: Wednesday 08 April 10:00 - 12:00 EDT (Timezone: Eastern Daylight Time)
*Time: Wednesday 03 June 2009 10:00 - 12:00 EDT (Timezone: Eastern Daylight Time)
*Where: irc://irc.freenode.net#sugar-meeting
*Where: irc://irc.freenode.net#sugar-meeting
We will be doing a testing session tomorrow. Bring the latest Soas (F11) image [1] ready downloaded and flashed on a stick with you.
We will be doing a testing session. Bring the latest Soas (F11) image [1] ready downloaded and flashed on a stick with you.
(join the session at any time)
(join the session at any time)
====Testing====
====Testing====
Some call it failure testing some stress testing. We want to meet next Wednesday to find the bugs left in Sucrose 0.84 to be able to fix them for 0.84.1 We will use the latest Sugar on a Stick for those efforts. Please watch here for announcements.
Some call it failure testing some stress testing. We want to meet next Wednesday to find the bugs left in Sucrose 0.84 to be able to fix them for 0.85.1 We will use the latest Sugar on a Stick for those efforts. Please watch here for announcements.
====Triaging====
====Triaging====
I still wonder how we can handle the Soas component in trac best. We would need different versions and milestones for each component. We could add things like: ‘Sucrose 0.84′, ‘Soas-1′… But this would not be optimal. Idealy, when we have a ticket in the component Soas we would only have the milestones available to select which belongs to that component. If anyone knows how to do that in trac - please comment.
I still wonder how we can handle the Soas component in trac best. We would need different versions and milestones for each component. We could add things like: ‘Sucrose 0.84′, ‘Soas-1′… But this would not be optimal. Idealy, when we have a ticket in the component Soas we would only have the milestones available to select which belongs to that component. If anyone knows how to do that in trac - please comment.
: See http://trac.edgewall.org/wiki/TracFaq#can-i-manage-multiple-projects-from-a-single-installation-of-trac and http://trac.edgewall.org/wiki/TracMultipleProjects
We have been started last week to give a [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=component&col=type&col=severity&col=status_field homework] assignment from Trac. This week we want to verify the Soas bugs. Do they belong into this component? Or do they describe a bug that is actually in one of the Sucrose components? Do we have enough information from the reporter? Is the severity set correctly? And of course the favorite one - is it a duplicate?
We have been started last week to give a [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=component&col=type&col=severity&col=status_field homework] assignment from Trac. This week we want to verify the Soas bugs. Do they belong into this component? Or do they describe a bug that is actually in one of the Sucrose components? Do we have enough information from the reporter? Is the severity set correctly? And of course the favorite one - is it a duplicate?
Simon recaps the weekly work in his blog [http://erikos.sweettimez.de/ Sugar Beets]
Simon recaps the weekly work in his blog [http://erikos.sweettimez.de/ Sugar Beets]
===Archives===
===Archives===
* Triaging [http://meeting.laptop.org/sugar-meeting.log.20090527_1210.html 27 May 2009], [http://meeting.laptop.org/sugar-meeting.log.20090527_1210.html log]
See [[BugSquad/Meetings/Agendas]], and [[BugSquad/Meetings/Minutes]] for archives.
See [[BugSquad/Meetings/Agendas]], and [[BugSquad/Meetings/Minutes]] for archives.