List of Planned 2.9.0 Changes
Document in Progress
Planning for the 2.9 release has just begun. Check back frequently for updates.
Timeline
A timeline for the 2.9.0 release has not yet been drafted.
Key dates
Action |
Date |
|---|---|
Major changes |
|
Code Freeze |
2011-09-21 |
Alpha tag |
|
Beta tag |
|
String freeze |
|
Release Candidate Tag |
|
Decision Point for Release |
2012-02-14 |
Software Release |
2012-03-01 |
Current "Big" Proposals
Additions
JIRA |
Proposer |
Description of addition proposal |
Notes |
Status |
|---|---|---|---|---|
| SAK-20344 - Getting issue details... STATUS | Add Excel and CSV user import to site info tool |
Be carefull with CSV and handling of UTF-8. Maybe providing support for OpenDocument format's ods could replace CSV. |
Assigned to Adrian Fish. Not started. |
|
| SAK-19813 - Getting issue details... STATUS | NeoPortal: new portal and includes Adrian Fish's floating chat as an extension |
|
|
|
|
Lesson Builder (Rutgers) |
|
||
Mailsender (replaces now-deprecated Mailtool) |
In production at various places |
|||
new Roster tool (Lancaster) |
deferred from 2.8 |
|||
updated Blog tool from Lancaster. Rewrite of original Blog tool in JS/Trimpath. |
deferred from 2.8 |
|||
| KNL-739 - Getting issue details... STATUS | Allow dynamic reloading of ServerConfigurationService properties and component manager primitives |
|
||
| SAK-20552 - Getting issue details... STATUS | Grading all section members once |
To be able to grade all section members without the need of selecting them one by one. The process can be the following: |
|
|
| SAK-20554 - Getting issue details... STATUS | Assignment section filter in grade report |
|
|
|
| SAK-20555 - Getting issue details... STATUS | New assignment type: audio recording |
Our instructors demand a new type of assignment, audio recording, in the same way Samigo (Test&Quizzes) provides. |
|
|
| SAK-20556 - Getting issue details... STATUS | Assignments Zip Export doesn't preserve UTF8 names |
The download all functionality doesn't preserve the display of names with utf8 characters. |
|
|
| SAM-1197 - Getting issue details... STATUS | Multiple choice, multiple answer with penalty |
Currently, each correct answer adds points and each wrong answer discount points. Thus, if you create a new question with three possible answers but only two of them being correct, if the students marks the three he/she will get 2/3 of the total points when, probably, he/she should be assigned zero points. Then our instructors have requested us to choose between: |
|
|
| SAK-20558 - Getting issue details... STATUS | Sending the same feedback comment to a set of users |
In the same way that you can select user to select users and allow resubmission to a reduced set of users, our instructors have requested to be able to send the same feedback comment to a set of users, independently if they are in same section or not. |
|
|
| SAK-20559 - Getting issue details... STATUS | Searching using wildcards |
Sakai offers several tools where user can enter a text and ask for a search of users, sites, sections and so on. It would be useful to be able to use wildcards in this searches. For example, if you enter "Discussion % SMPL101", you'll get: |
|
|
Promote UFP sakai-feeds |
promote the feature richer UFP-contributed newsfeeds and deprecate the old news tool |
|||
SAK-1525 - Getting issue details... STATUS / KNL-309 - Getting issue details... STATUS |
soft-delete files/resources from content hosting (and purging) |
Running in 2.5 and 2.6 at Oxford and Columbia (perhaps other places) |
||
| SAK-19952 - Getting issue details... STATUS | soft-delete sites with with purging (30 days by default) |
|
||
KNL-273 - Getting issue details... STATUS / SAK-800 - Getting issue details... STATUS |
Sam Ottenhoff |
Upload and unroll ZIP files |
Big request from prospective Sakai institutions. Have addressed performance concerns in patches. Off by default. |
Deprecations and Removals
JIRA |
Proposer |
Description of addition proposal |
Notes |
Status |
|---|---|---|---|---|
|
|
Complete removal of OSP Warehouse (No user facing components). OSP dependency an issue |
|
|
|
|
Remove Profile "classic" (addition of roster2 renders it redundant). |
|
|
Architectural and library changes
What |
JIRA |
Description |
Notes |
Status |
|---|---|---|---|---|
Tomcat 6 |
|
Move to Tomcat 6 |
I believe we should target Tomcat 7 instead (SS) |
|
JDK 1.6 |
SAK-20089 - Getting issue details... STATUS | Require Java 1.6 |
|
In Progress |
support for Oracle 9i |
|
Deprecate support for Oracle 9i |
We could deprecate SPECIFIC Oracle9 support after, for example, the 2.8 release. In this case, the deprecation means that we don't guarantee that stuff - mostly conversions I expect - will work in Oracle9 past that time and that we are free to use Oracle10+-isms at any moment. We would need to communicate this early, often, and as widely as possible. In addition, we would probably need to offer solid advice on moving from LONGs to LOBs and making sure that OOTB Sakai doesn't create LONGS or other older/deprecated data types like DATE (use TIMESTAMP)." |
Will occur after 2.8 release |
JSF |
SAK-19282
-
Getting issue details...
STATUS
|
Upgrade to jsf 1.1_02 |
|
Completed-ish (many tools need review) |
JSF |
SAK-20086 - Getting issue details... STATUS | Upgrade JSF project to laters 1.2 release (1.2_15) |
|
Under discussion / Needs resources |
support for IBM DB2 |
|
Officially remove support for IBM DB2 if no one in the community is ready to do it and cleanup the official code |
Discussion delayed because we were working on 2.8 and waiting for news from IBM. Audit is done in SAK-20243 - Getting issue details... STATUS |
Get news and discuss |
support for IBM WebSphere Application Server |
|
Officially remove support for IBM WebSphere Application Server if no one in the community is ready to do it and cleanup the official code |
Discussion delayed because we were working on 2.8 and waiting for news from IBM. Audit is done in SAK-20243 - Getting issue details... STATUS |
Get news and discuss |
Maven 3.0.3 |
|
Move to Maven 3 |
at minimum make Maven 2.2.1 the minimum version required. |
|
DBCP |
Upgrade to DBCP 1.4 |
DBCP requires java 1.6 |
Project-Specific Updates
Sakai Monolithic
Project |
Lead |
Bug Fixes (Yes/No) |
API Changes? (Yes/No) |
Enhancements List (w/ SAK) |
API Changes? |
Notes |
|---|---|---|---|---|---|---|
Announcements |
Yes |
No |
- Add announcement API support in Entity Broker (SAK-18764) |
|
|
|
Assignments |
|
|
|
|
|
|
BasicLTI |
|
|
|
|
|
|
Chat |
Maintenance Team |
|
|
|
|
|
Calendar Summary |
Maintenance Team |
|
|
|
|
|
Citations |
|
|
|
|
|
|
Email Archive |
|
|
|
|
|
|
Email template service |
|
|
|
|
|
|
Gradebook |
|
|
|
|
|
|
I18n |
|
|
|
|
|
|
Linktool |
|
|
|
|
|
|
OSP |
|
|
|
|
|
|
Podcasts |
|
|
|
|
|
|
Portal |
|
|
|
|
|
|
Post'Em |
|
|
|
|
|
|
Preferences |
Maintenance Team |
|
|
|
|
|
Quartz Scheduler |
Maintenance Team |
|
|
|
|
|
Roster |
Maintenance Team |
|
|
|
|
|
Resources, Drop Box |
Maintenance Team |
|
|
|
|
|
rWiki |
|
|
|
|
|
|
Syllabus |
[~gjthomas] |
|
|
|
|
|
Schedule |
|
|
|
|
|
|
Site Info |
|
|
|
|
|
|
WebDAV |
|
|
|
|
|
|
Worksite Setup |
|
|
|
|
|
|
WYSIWYG Editor |
|
|
|
|
|
|
|
|
|
|
|
|
|
Independent Releases for inclusion in 2.9.0 Distribution
Project |
Lead |
Bug Fixes (Yes / No) |
API Changes?(Yes / No) |
Enhancements List (w/ SAK) |
Version |
Notes |
|
|---|---|---|---|---|---|---|---|
common |
|
|
|
|
|
|
|
content-review |
|
|
|
|
|
||
edu-services |
|
|
|
|
|
||
Entity Broker |
|
|
|
|
|
||
hybrid |
|
|
|
|
|
|
|
Kernel |
|
|
|
|
|||
Message Center |
[~wagnermr] |
|
|
|
|
|
|
Samigo (Aka Tests & Quizzes) |
|
|
|
|
|
||
Profile2 |
Yes |
Yes |
Abandon SakaiPerson. Reimplement. (PRFL-230) |
1.5.0 |
|
||
Polls |
|
|
|
|
|
||
Reset Password |
David Horwitz |
|
|
|
|
|
|
purepoms |
|
|
|
|
|
|
|
Search |
|
|
|
|
|
||
Site Stats |
Maintenance Team |
|
|
|
|
|
|
Web services |
Yes |
No (but there are new services) |
TBA |
|
|
Packaging changes
*1. Move entitybroker into the kernel.
*2. Move common into the kernel.
Other miscellaneous 2.x Changes
The following "scenarios" should also be considered for future 2.x releases (posted by Anthony Whyte after Denver Project Coordination Discussions):
1. Refactor JSF tools that fail to compile in Java 1.6 so that we can eliminate the need the specify the workaround system property
-Dsun.lang.ClassLoader.allowArraySyntax=true.
- TCC Discussion: The move to Tomcat 6 and Java 1.6 was discussed at length on 18 August 2010. It seems that trying to make the required changes to move to Tomcat 6 and use Java 1.6 without any -D workarounds is too aggressive for 2.8.
- Comment on 8/31/10 from Charles Hedrick: Why do we object to using -D? Mightn't we be better off to use Tomcat 6 with -D than continue with Tomcat 5.5?
- +1 Mustansar Mehmood
- Charles Severance: I think the Tomcat 5 / 6 Discussion centered less around the -D and more around the worry that there would be little issues that would pop up that would be hard to find, reproduce, track and fix. It seemed like the first attempts at T6 failed and folks decided to focus elsewhere. So we don't have any data that gives us confidence that T6 is an "easy switch".If no one chooses to run T6 and then report that T6 works solidly with no strange glitches - we will find ourselves in the same place for 2.9.
2. Refactor Portfolio and other tools in order to eliminate the need to specify the workaround system property
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false required
since Tomcat 5.5.27.
3. Rework Sakai deployment patterns (e.g., target=/lib) so that we can upgrade to Tomcat 6.0.
- This may not be necessary as you can just updated the shared classloader config in conf/catalina.properties to:
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*.jar
4. Add mailsender as a possible replacement for the retired mailtool.
- Comment from Clay Fenlason: Re: mailtool. It should be removed, but it's less clear that mailsender should replace it. Mailsender has no maintainer either, it just happens to be in better shape codewise. Would the maintenance team be prepared to support it?
- Comment from Jean-François Lévêque (2011-05-26): Even if the official maintenance of Mailsender question is valid, this project seems active with Carl helped by Seth and contributions to maven packaging by Anthony.
5. Deprecate linktool (replaced by basiclti)
- Comment from Stephen Marquard: On #6, basiclti is not equivalent or better than LinkTool. They have different security models, and in some respects that of LinkTool is stronger than basiclti's. There is also some functionality for getting Sakai sessions through webservices that's not in basiclti. So I don't think it will be possible to deprecate LinkTool anytime soon, especially as basiclti's capabilities may be limited to what the standard supports.
Comment from Charles Severance: I see no reason to deprecate LinkTool as it is not a maintenance concern and man... I see no reason to deprecate LinkTool as it is not a maintenance concern and many folks are using it in production and while Basic LTI provides equivalent information to LinkTool, BasicLTI is not a direct replacement for LinkTool. We can have the debate as to which is more secure over beers But again, the upshot is I recommend against deprecating LinkTool in 2.8. - Comment from Anthony Whyte: The question of deprecation (e.g., stealthing a tool in the next release (2.8) and then removing it from the release that follows (2.9)) is a question separate from whether or not it's a maintenance concern (currently Stephen maintains it). I posed the scenario in order to surface discussion regarding whether or not basiclti (or LTI) can provide equivalent functionality in 2012 that renders it redundant.
6. Review tools that do not implement fine-grained permissions and correct as necessary.
7. Review tools that are not group aware and correct as necessary.
8. Review tools that do not auto-register events with sitestats (via the entitybroker) and implement as necessary.
9. Review tools that could benefit from the addition of entitybroker providers and implement as necessary.
10. Convert portfolios (osp) to an indie release; the assignment tool might also benefit by moving to its own release schedule.
- The conversion of OSP to an independent release was discussed, but it depends on the release of Assignments as an indie as well.
- Comment from Mustansar Mehmood: Independent release of OSP is a great idea like samigo
11. Make portfolios i18N friendly.
12. Email Archive Enhancements (Wish list / development work without plans or resources)
- Checkboxes for multiple deletion and sending
- Performance improvements
13. Entity Broker Enhancements (Wish list / development work without plans or resources)
- Search Integration
- Archive Integration
14. Gradebook
15. Assigments2 inclusion in foundation distribution.