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="6d3792a5c413e92b-024498e8-41ea4365-88b59a83-b605616bbbdf9662397e2602"><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>

...

  • For unresolved issues, which are still being worked on, the fix version is set to the "whole" release number (e.g., 2.1.0, 2.1.1, 2.2.0) in which the issue is expected to be resolved. For resolved issues, the fix version is initially set to the actual interim QA release number (e.g., 2.1Generally, this is is the next version's first QA release, such as 2.3.0.001, 2.1.0.002) in which the issue was resolvedj..
  • For resolved issues, developers should set the fix version to "Nightly/SVN-trunk", unless they know for sure what release the fix will be incorporated in. As perparations are made for each QA release, the fix version will be updated appropriately. (QA folks will also double-check the fix version at verifcation time to ensure that it is correctly set relative to the release they are testing.)

After a release is made, the interim QA release versions are merged into the last QA "whole" version release number for clarity, (i.e.. For example, 2.2.1.0.001, 2.1.0.002, 2.1.0.003002, and 2.1.0.004 and 2.1.0.005 were 003, were the three QA releases for that version, and they were merged into 2.2.1. 0.006), and that version is renamed to the release version (i.e., 2.1.0).The merging is important in keeping it simple to search, filter, and view issues for released versions of Sakai.

Further notes on Version Numbers

...