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="c848de763de39d4b-f52c4685-41754a16-9938a95b-be98b3d7658f6a4960c2e601"><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>

...

Further notes on Version Numbers

...

  • Branch versions as Affects Versions (e.g., Nightly/SVN-Trunk, 2.3.x, 2.4.x) – Limit the use of a branch version as an Affects Version to when the same issue is known to not be present in a previously tagged version. This is important because branch versions are moving targets, what is Nightly/SVN-Trunk one day is not necessarily the same the next, so it is genereanlly more important to know if an issue affects a released version. Also, such issues are treated as transient issues and will not necessarily need to consume valuable QA resources once they are resolved.
  • Branch versions as Fix Versions (e.g., Nightly/SVN-Trunk, 2.3.x, 2.4.x) – As fixes are checked into a branch,

...

  • they should have their Fix Version updated from the version the issue was estimated to be addressed in (e.g., "2.4.0 Tentative") to the branch's version (e.g., Nighlty/SVN-Trunk). 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 place in the shared Jira filters.

Maintenance Branch Version Numbers

...