r1 - 29 Apr 2005 - 15:58:41 - PhilippeBossutYou are here: OSAF >  Projects Web  >  DevelopmentHome > ApplicationProject > BugzillaTracking > Bugzilla20050428

Notes from the Bugzilla Tracking meeting

Attendees : all App team - Date : Thrusday April 28th, 2005

Dependencies and Risks

  • AE (Attribute Editor) : Notifications : Depends on Ted
  • DV : Font Spec : we need to write a technical spec
  • wxWidgets : Shadow and Grid are both big and somewhat risky

Assignment

  • Recurrence : Alec : need someone as a back up (paternity). Biggest riskiest effort of 0.6
  • Sharing : John : need to sync up with Morgen on what we (App) need to deliver (update: Philippe checked this morning with Morgen and, so far, no App task linked to sharing identifiable). Risk of spill on DV.
  • CPIA : John
  • Perf : Donn : sync up with Katie, check the keyword == perf bugs already logged and not fixed, log some as needs be (e.g. Start up time on Mac)
  • Journaling : Donn : spec to write, share spec with Aparna and Heikki (QA)

Tasks to perform in Bugzilla

To do now (Philippe and Heiki) : update Bugzilla as appropriate in particular:

  • Components : Update the components list and add: Application: Behavior, Application: Sidebar, Application: Trash and Deletion, Application: Drag and Drop, Calendar: Recurrence, Calendar: Minical, Journaling
  • Set milestones and releases for 0.6
  • Move bugs we won't address for sure to 0.7 and future
  • Use the full priority range (make sure then that what's punted is marked for release 0.7)
  • Get QA buy off to set severity more consistently
  • Make task a keyword, not a flag

To do now (All) : as soon as the here above is done :

  • Create tasks records in Bugzilla: each dev is reponsible to create its list of tasks (we went through this exercise once so it's mostly entering those in)
  • Philippe : create reports and graphs accessible from the App Team page

To do later (Heikki or someone in Heikki's team) : the stuff here under requires Bugzilla hacking and coding

  • Set hardware off or just don't display it (confusing and irrelevant to us)
  • Add a field so that devs can number the bugs according to their schedule (create an ordered list of bugs)
  • SWAG : add a combo box in the bug editing form that will populate the Est. Orig. automatically

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.