Difference between revisions of "DSDP/TM/Committer Phone Meeting 23-May-2006"

Revision as of 10:32, 22 May 2006

Meeting Title:	TM Committer Phone Meeting
Date & Time:	Tuesday June 23, 2006 at 6.30am PDT / 9.30am Toronto / 3.30pm Salzburg
Dial-in:	Skype martin.oberhuber

Fixed-line fallback dial-in:

M2 Process Review
- Distracted by changing topics?
- Stressed finishing up M2?
- Process Improvements for M3?
Bugzilla usage, tips and tricks
- Want to use markups like [api], [apidoc] -- others?
- How to find a bug to work on: Bugzilla Status / Assignee / Severity
- Using Bookmarks (from TM home page and M2 build notes, saved searches, change-multiple-at-once
- How to fix a bug: commit comment, when to mark fixed
- How to verify and close
IP Due Diligence
- How to apply a patch
- How to add legacy code
M3 Planning and Priorities
- Assign tasks to individual committers?
- 1. Start EMO Review for all upcoming legacy contributions:
  - Docs, user commands, import/export, anything else?
- 2. Add Examples to CVS
- 3. Add Unit Test Framework
- 4. Fix critical, major and obvious bugs; add unit test for bug where appropriate; how to mark bugs deferred? (Priority or target milestone)
- 5. Start daily driver schedule - prepare driver for M3 deliverables early
- 6. Make Wizard completely replacable
- 7. UI/Non-UI Refactoring; API improvements; fix "hard" bugs
- 8. Work on ISV Docs
- RSE API Discussions
- RSE 2.0 Planning
Want regular committer meetings?

@@ Line 34: / Line 34: @@
 ** How to add legacy code
 * M3 Planning and Priorities
+** Assign tasks to individual committers?
 ** '''1.''' Start EMO Review for '''all''' upcoming legacy contributions:
 *** Docs, user commands, import/export, anything else?
@@ Line 43: / Line 44: @@
 ** '''7.''' UI/Non-UI Refactoring; API improvements; fix "hard" bugs
 ** '''8.''' Work on ISV Docs
-** Assign tasks to individual committers?
 ** [[RSE API Discussions]]
 ** [[RSE 2.0 Planning]]
 * Want regular committer meetings?