Symbian developer community

 
Home > Wiki > Symbian^2 Defect Scrub
wiki

Symbian^2 Defect Scrub

From Symbian Developer Community

Jump to: navigation, search

We are now nearing the end of the hardening phase for Symbian^2. This means that the community is concluding their productisation efforts and it is ready to move the release into a “Stable” condition. Only contributions associated to critical defects will be accepted. It also signals that the community at large should focus on hardening Symbian^3.

We have around 160+ defects still open against Symbian^2. Normally, community activity (package owners and contributors) would take care of them. However, Symbian^2 is still in start-up mode and this has not happened. So, We have 2 choices, leave the bugs where they are or clean them up.

To make sure that Bugtracker does not accumulate so much noise that renders itself useless for quality management in the future, the Release Council agreed to sponsor a”Defect Scrub” exercise.

To facilitate the exercise (scheduled for wk06), we have review all open defect applying the following guidelines:

  • If a patch or FCL fix has been provided the defect is to be fixed in S^2 (unless code review fails)
  • If a defect is still relevant for S^3 it will be propagated
  • Propagated defects will be tagged: a defect can not be propagated twice.
  • Unclear defects will be tagged for further analysis (this includes BC grey issues)
  • Defects with severity = “minor” will be closed as “wontfix” if the community has not provided a fix by “Stable”


Contents


Join the discussion

You can join us on the Release Council forum

Participants

  • Juha Malkki - Digia - comments via email
  • Chandra Narayanasamy - Fujitsu **
  • Thomas Whitson - Accenture (on behalf of Docomo)
  • Theodoros Galanis - Accenture (on behalf of Docomo) **
  • Juan de Miguel (Elektrobit) **
  • Kari Lammi (Nokia) **
  • Richard Baruch - Symbian Foundation **
  • Victor Palau - Symbian Foundation (Chair) **
  • Laurent Le Gal - Texas Instruments - appologies sent

**participated in the call

Scrub workshop 12th Feb

The material

Pre-call

  • zip file containing:
    • .xlsx with the defect information
    • .pptx with an introduction to the scrub

Output

Notes on the xls:

  • Entries with significant changes in bugtraker are highlighted in amber
  • Closed entry are in grey
  • Entries that Accenture had an interest on have a cell in Blue
  • Entries that Fujitsu had an interest on have a cell in Red(ish)
  • Action column denotes carry over actions for the next call

Meeting Timing and Agenda

Time:Friday 12th Feb - 10 -12 UK time (12-2pm Finish time) Location: Webex+confcall

Agenda:

  • Introduction - 10 min
  • Agree aim of Scrub (review objective and guidelines)- 20 min
  • Agree timeline to implement scrub - 10 min
  • Who has the responsibility to fix defects in a release
    • Nokia PkO contribution acceptance - 20 min
  • review defects - 1hour
    • Proposed Won't Fix Defects that a participant has a comment for
    • Review any critical and major (current or proposed) bugs that a participant has a comment for
    • Any other comments
    • Agree Actions

Summary of the call

We managed to run on schedule which on itself is a great achievement!

The group spend some time discussing the ppt material, in specific the intend of the scrub meeting and the guidelines applied to the pre-analysis. We took the following decisions:

  • We agreed on the scope of the scrub as described in the ppt document
  • We agreed on the rules applied to the pre-analysis as valid for the scrub
  • We agreed that the timing for applying the recommend actions should be asap
    • we also agree to give some time for defects that have been recently created before acting on them

We discussed at length the responsibility on fixing open defects. The responsibility is for the community to provide fixes, and lack of fixes might mean lack of interest on the issue. The Package Owner (PkO) is responsible for reviewing the proposed solutions and integrate them to the MCL, the PkO can choose to delegate these responsibilities.

We also reviewed all bugs that scrub participants had specific comments on (Note that at this point Chandra from Fujitsu joined the call). The outcome of this discussion is capture on the xls above.

We agreed the following actions:

  • Symbian to implement the recommended changes - done
  • chaise the Symbian bugs - Victor
  • Chandra to ask pko for 1398 if the missing files that are now present in S^3 can be copied into the S^2 RCL -Done
  • Chandra to ask Fujitsu teams if they can provide further details to 144 , and possibly a fix or workaround - Done defect not a priority can be closed
  • Theo to check if patches can be provided for 398,397,399,114,401,402,396,331 and 1413
  • RichardB to check status of 805 -Done
  • Victor to write to all PkOs with proposed fixes and instructions on how to integrate them - done
  • Victor to check with Nokia the reason for the missing files in BUG69 - done
  • Victor to reassign 484 to the IDE team - done
  • Victor to add Digia's BC break feedback to the bugtracker entries - done
  • Kari to chaise pkos on reviewing proposed fixes
  • Victor to chaise qemu contributions
  • Chandra to propagate proposed

We will meet in a few weeks to review the progress on these actions

Retrieved from "http://developer.symbian.org/wiki/index.php/Symbian%5E2_Defect_Scrub"

Sign in to comment…