Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue Type

Definition for Sakai

Bug

An error in design or implementation which directly impedes a user from achieving their expected result.

Task

A new capability being added to Sakai.

Feature Request/Requirement

A desired capability, for inclusion in a future release of Sakai; ideas that come with resources interested in implementing them are more likely to be developed than those offered with the hope that someone else will step forward to do the work.

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d8e4bcec75dff080-cd2ba1d2-42a44481-b69dbb12-9f0396f5144d0f17c27f34ef"><ac:plain-text-body><![CDATA[

Contributed Patch

A community-contributed patch to a particular version of sakai. The origin of such issues may lie in Bugs or Feature Requests which Sakai has not yet evaluated for implementation. Under such circumstances a linked issue is generally created by cloning the orignal issue in order to track Sakai's work on the issue. [Use at your own risk!]

]]></ac:plain-text-body></ac:structured-macro>

...

Anchor
Designers and Developers
Designers and Developers
Designers and Developers

Planning

  1. As new issues come in and as you periodically review the status of existing issues, use the Fix Version to indicate for what version you expect to implement a solution for the issue.
    • Notes on future versions:
      • Leave the Fix Version as Unknown if you are not sure what version the issue will be addressed for.
      • Set the Fix Version to the first QA release version (e.g., 2.2.1.001) to indicate an issue will be addressed for that release.

Addressing an Issue

  1. Assign a Bug or Task to yourself to work on.
  2. Work on the issue, updating, modifying, re-asssigning, etc. as necessary to achieve resolution.
  3. When work is complete, Resolve the issue as Fixed (or other appropriate resolution, such as "Won't Fix", if necessary) and set the Fix Version to "Nightly/SVN-Trunk".
    • Notes on setting Fix Version:
      • In general set the Fix Version to "Nightly/SVN-Trunk", unless you know a fix is intended for and will be included in a specific version, then use that.
      • At Feature Freeze, all the resolved issues are evaluated for inclusion in the release, and those that are selected have their Fix Version updated, if necessary, from Nighlty to the first interim QA release (e.g., 2.1.0.001).
      • After Feature Freeze, and during QA, if an issue is intended for a specific interim release, then the Fix Version can be set appropriately (e.g., 2.1.0.003), or, if it is unclear, set it to Nightly/SVN-Trunk (and the release team or QA team will update it as necessary).
  4. For Tasks, if there is nothing explicit for the QA team to test, then please Close the issue. Otherwise, for Bugs, just leave the issue as Resolved, and the QA team will Close it after it passes testing, or Reopen it for further development.

...