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.
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="fd357ae0cefd359b-1d119528-4a114767-a9acb5db-6b285abc0c9156a39418f2c6"><ac:plain-text-body><![CDATA[
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!]
- Affects Version - Version in which an issue is observed. This should never be set to a "future" version of Sakai, e.g., Post-2.1.2; issues should only affect Sakai relative to a known existing version.
- Fix Version - Version in which an issue is resolved. This could be a "future" version of Sakai, when indicating a future release you expect an issue to be resolved in.
Both of these versions, however, are not necessarily meaningful for all issue types. The table below summarizes how they are used in the context of specific issue types.
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"; for issues encoutered on a production/maintenance branch that is not yet in QA, report the Affects Version as <version>. 000 (e.g., 2.1.0.000, 2.1.1.000). When such issues are resolved prior to QA, the Fix Version is similar similarly set, which helps identify potentially transient issues that might not need full attention during QA.