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="7e19631a1bb10da5-4bd6ac7c-43c94309-9821b12e-644e7552b73fcd2ce8a8e1d8"><ac:plain-text-body><![CDATA[

Image Removed Image Added 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 original issue in order to track Sakai's work on the issue. [Use at your own risk!]

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

Image Added Branch

An experimental branch of code, which may or may not be merged back into the main code after the experiment completes; identified in SVN by a branch named with the Jira Key.

Anchor
Status
Status
Status

Status

Definition for Sakai

Open

Issue is under consideration.

In Progress

Issue is actively being worked on.

Reopened

Issue was thought to be resolved, however, it did not pass QA and needs further work.

Resolved

Issue has been addressed and is ready for testing.

Closed

Work on issue is complete and has passed testing.

...

  • Branch versions as Fix Versions (e.g., Nightly/SVN-Trunk, 2.3.x, 2.4.x) – Generally the only branch version a developer needs to be concerned with is Nightly/SVN-Trunk. Only the Branch Manager or project team members dealing with maintenance branches will need to worry about adding other branch versions (e.g., 2.3.x, 2.4.x) as Fix Versions; and, those versions should only be used when the fix is actually checked-in to the branch, it should not be used as an indication that one would like a fix checked-in. This will ensure that the issue continues to appear listed in the correct Jira filters.
  • SAK Experimental Branches (i.e., branch) – Use the generic "branch" version as the Target or Fix Version when working on subtasks under a SAK Experimental Branch. If and when the branch is merged into trunk, please rememer to update the Fix Version to the standard "Nightly/SVN-trunk" (or the appropriate maintenance branch version, if that's where its being merged).

Maintenance Branch Version Numbers

...