Versions Compared


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


Issue Type

Definition for Sakai


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


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="91afd8e3431e8341-8f534cc8-46a64cd3-99e5a988-3f69773214b68ba26e3a6c79"><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!]



When development work predominates on a branch – prior to a the branch entering QA – the version number to report issues against is basically a moving target. In other words, as fixes are checked into a branch, there is currently no change in the version used to refer to that branch; the SVN revision number, however, does change, so use that if you need to track that level of granuliarty. For instance, for issues encountered on the trunk branch, report the Affects Version as "Nightly/SVN-Trunk. When such issues are resolved prior to QA, the Fix Version is similarly set, which helps identify potentially transient issues that might not need full attention during QA.

Maintenance Branch Version Numbers

A ".x" version is used to track issues relating to maintenance branches. For instance, 2.2.x is the version number representing the post-2.2.2 release maintenance branch. This version number should only be used by the maintenance branch manager as a Fix Version. It is used to indicate that for a particular Jira the associated revisions have also been merged into the maintenance branch, in addition to trunk.

If someone is running the maintenance branch, then it may be used as an Affects Version, however, be forewarned of the potential for confusion since the maintenance branch is a moving target. In such a situation it is important to indidate the revision number in the Environment field, so that folks know to which version of the maintenance branch you are referrning.