Versions Compared

Key

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

...

Anchor
Definitions
Definitions
Definitions

...

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

A desired capability, which may be selected for implementation in a future release of Sakai.

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="747a7d6380edd0a0-14e4fe65-400f462a-afebbaa1-5a7cb36055dff40e00d6c1a7"><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
Summary
Summary
Summary

  • A brief statement summarizing the issue. (Field is limited to < 255 characters.)

Anchor
Environemnt
Environemnt
Environment

  • A description of the Sakai enivronment in which the issues was encountered, e.g., web browser, operatings system on which Sakai is installed.
  • For QA participants this is a good place to note on which test server the issue occurred (e.g., MIT Stable HSQL, MIT Stable Oracle, MIT Stable MysQL, Nightly)

Anchor
Desription
Desription
Description

  • A detailed description of the issue, including the steps necessary for reproducing the issue.
  • You can also add attachments, including screen shots to help illustrate the issue.

Anchor
Component
Component
Component

  • The particular part or parts of Sakai related to the issue.

Anchor
Security Level
Security Level
Security Level

  • Controls the visibility of the issue; currently toggles between viewable by anyone or by just the committers and testers (and the reporter of the issue).

Anchor
Workflow
Workflow
General Workflow

...

General Workflow for Teams/Tasks

Anchor
Requirements
Requirements
Requirements/Design

The workflow for the requirements process (post Sakai 2.1 release) is being developed in the Sakai Working Group: Requirements Process.

Anchor
Designers and Developers
Designers and Developers
Designers and Developers

  1. A Bug or Task issue is assigned to someone to work on.
  2. Work begins on issue. Issue is updated, modified, re-assigned, etc. as necessary to achieve resolution.
  3. When work is done, Issue is resolved as "Fixed" (or "Won't Fix" if necessary), and meta-data fields are updated accordingly:
    • Fix Version:
      • In general the Fix Version is set to "Nightly/SVN-Trunk".
      • At Feature Freeze, all the resolved issues are evaluated for inclusion in the release, and those that are selected have their Fix Version updated to the first interim release (e.g., 2.1.0.001).
      • Afater Feature Freeze, and during QA, if an issue is intended for a specific interim release, then the Fix Version is set to the appropriate iterim release (e.g., 2.1.0.002), or, if it is unclear to Nightly/SVN-Trunk (and the release team will update it as necessary).

Anchor
Quality Assurance
Quality Assurance
Quality Assurance (QA)

  1. QA personnel select an appropriate issue from the list of issues "QA Awaiting Verification".
  2. An attempt is made to verify the issue.
    • If it passes verification, then it is Closed.
    • If it fails verification, then it is Reopened.
      • If is not clear to whom the issue needs to be re-assigned, then assign it to default.
    • Some issues can not be easily verified and may require special testing conidtions or input from developers, and further discussion is conducted as necessary.