Sakai 2.4.0
General Information
Release Manager: ~lance@indiana.edu
Questions on the release? Email sakai-dev@collab.sakaiproject.org.
Release Discussions
QA
See /wiki/spaces/QA/pages/6806601733.
Tool Promotions
With each Sakai release tool projects are evaluated for promotion from their current status level to Provisional and Core status. Follow the Discussion links below to view an evaluation of how the tool stacks up against the Criteria for Provisional Status, as well as to view discussion from users of the tool.
The final discussion and decisions on tool promotion were carried out during the QA-Release meeting on 14-March-2007.
Tool |
Current Status |
Proposed Status |
Confluence Page for Discussion |
Jira Issue |
Decision |
---|---|---|---|---|---|
Contrib |
Provisional |
No. Not ready yet. |
|||
Contrib |
Provisional |
No. JForum team had insufficient time and resources, but will try to for the next release again. |
|||
Contrib |
Provisional |
Yes. Will handle QA and test plan and produce docs by code freeze. |
|||
Provisional |
Core |
Yes |
|||
Contrib |
Provisional |
Yes. Will provide help documents. Still waiting on CCLA, have CLAs. |
|||
Provisional |
Core |
No. Consensus is that it is not running in Production in enough places yet and should develop a stronger track record before promotion to Core. Everything else looks good. |
|||
Contrib |
Provisional |
Yes. Some concern about UI issues, however, desire for functionality at Provisional level was deemed greater. |
|||
Provisional |
Core |
Yes. |
|||
Contrib |
Proivisional |
No. Dependencies between PreferAble and new Portal code have been elminiated, which was the main reason it was being considered for promotion. Has not actually been run in production anywhere yet. |
|||
Contrib |
Provisional |
No. Insufficient resources to get it ready. Will aim for next release instead. |
|||
Contrib |
Provisional |
No. Concern regarding performance in production at large instutions. Test plan not ready. |
|||
Provisional |
Core |
Revisited during 18-Apr-2007 Release Meeting due to continued performance problems in prouduction settings. Decided to keep it as Provisional for 2.4. |
|||
Contrib |
Provisional |
Yes. Test plan and help will be developed. API issue still needs to be addressed before it can be Core, but users find it a very helpful as-is as an admin tool. |