- General Workflow
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="11ee3a8c15b6c423-a413435f-4ebb49d1-abb38ffc-12ef350a11e3356bc0a54bc9"><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!]
Both of these versions, however, are not necessarily meaningful for all issue types. The table below summarizes how these versions version categories are applied in Sakai for the various issues types.
The workflow for the requirements process for the Sakai Foundation (Post post Sakai 2.1 release) is undergoing development being developed in the Sakai Discussion Working Group: Requirements Process.
This workflow is aimed at those with commit privileges for Sakai.
- When resolving an issue set Fix Version to "SVN-Trunk" in general. After Feature Freezes and during the QA cycle, if your issue is intended for the release, set the Fix Version to.
- During QA