Typical Developer Work Flow

  1. Sit down at computer with coffee.
  2. Open Eclipse
  3. Open !BugZilla
  4. Using your saved search, find bugs assigned to you ( %MYBUGS{jkealey@shade.ca}% )
  5. Pick a bug to work on (or start thinking about).
  6. Change its Status from NEW to ASSIGNED
  7. Update files from SVN in Eclipse.
  8. Refer to UCMNavRequirements or UCMNavChangeRequests if in doubt exactly what has to be done.
  9. Perform work.
  10. Verify plug-in using test suite.
  11. Commit. Identify the bug number in the commit text.
  12. Within half an hour, a new build will be generated and tested. Email notification will be sent out to the team.
  13. Change bug's status in BugZilla to FIXED RESOLVED.
  14. If no more bugs are assigned to you, look for bugs that are assigned but new.

Typical Manager Tasks

  1. Review patch for bugs with status FIXED RESOLVED.
    1. If everything is approved, mark as CLOSED.
    2. If the bug is an enhancement, change status in UCMNavRequirements
  2. Review change requests
    1. If necessary, delegate research.
    2. Negociate repercussions of change.
    3. Approve/Reject change.
    4. Create bug in BugZilla, mark as Enhancement.
  3. Create enchancements in BugZilla for all requirements.
  4. When discrepancies are found between the requirements and the current build, file bugs in BugZilla.

-- JasonKealey - 08 Mar 2005
Topic revision: r2 - 24 Aug 2005, JasonKealey
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback