Child pages
  • List of Planned 2.9.0 Changes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Info
titleDocument 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

Jira
SAK-20344
SAK-20344

Adrian Fish

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.

Jira
SAK-19813
SAK-19813

Charles Severance

NeoPortal: new portal and includes Adrian Fish's floating chat as an extension

 

 

Jira
LSNBLDR
LSNBLDR

 

Lesson Builder (Rutgers)

Overview

 

Jira
MSND
MSND

Carl Hall
Seth Theriault

Mailsender (replaces now-deprecated Mailtool)

Overview

In production at various places

Jira
RSTR
RSTR

Daniel Robinson

new Roster tool (Lancaster)

Overview

deferred from 2.8

Jira
CLOG
CLOG

Adrian Fish

updated Blog tool from Lancaster. Rewrite of original Blog tool in JS/Trimpath.
Similar UI but improved functionality and backend

Overview

deferred from 2.8

Jira
KNL-739
KNL-739

John Bush

Allow dynamic reloading of ServerConfigurationService properties and component manager primitives

Proposal

 

Jira
SAK-20552
SAK-20552

David Roldán Martínez

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:
1) The instructor clicks at "Grade Section" (which needs be added to the current options: Edit, Duplicate, Grade).
2) The screen will be divided in two areas:
        2.1. Student submissions area: it will show student submissions and a text area to be able to send particular comments to each students of the section.
        2..2 Common area: instructor will be allowed to enter the same comments and grade that will arrive to all students in the section.

 

Jira
SAK-20554
SAK-20554

David Roldán Martínez

Assignment section filter in grade report

 

 

Jira
SAK-20555
SAK-20555

David Roldán Martínez

New assignment type: audio recording

Our instructors demand a new type of assignment, audio recording, in the same way Samigo (Test&Quizzes) provides.
Student will be display an applet to record him/her audio answer and instructor will be able to hear the audio answer and also to download the audio files in the submissions zip.

 

Jira
SAK-20556
SAK-20556

David Roldán Martínez

Assignments Zip Export doesn't preserve UTF8 names

The download all functionality doesn't preserve the display of names with utf8 characters.

 

Jira
SAM-1197
SAM-1197

David Roldán Martínez

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:
- If you need to mark all correct answer to get points in the question, otherwise you'll get a zero or the discount set up by the instructor.
- Each correct answer gives you points but wrong answer has a porportional penalty, i.e, if the whole penatly is 0.5 and the student marks only 2/3 correct answers, then he/she will get 0.5 * 1/3 = 0.16 as discount.

 

Jira
SAK-20558
SAK-20558

David Roldán Martínez

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.

 

Jira
SAK-20559
SAK-20559

David Roldán Martínez

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:
Discussion 1 SMPL101
Discussion 2 SMPL101
Discussion 3 SMPL101
Discussion 4 SMPL101
Or, if an i18n environment you write %iménez, you'll get Jiménez and Giménez (in Spanish both forms are correct).

 

Jira
NFS
NFS

David Horwitz

Promote UFP sakai-feeds

promote the feature richer UFP-contributed newsfeeds and deprecate the old news tool
NFS Overview

Jira
SAK-1525
SAK-1525
/
Jira
KNL-309
KNL-309

Matthew Buckett
Seth Theriault

soft-delete files/resources from content hosting (and purging)

Running in 2.5 and 2.6 at Oxford and Columbia (perhaps other places)

Jira
SAK-19952
SAK-19952

Steve Swinsburg

soft-delete sites with with purging (30 days by default)

 

Jira
KNL-273
KNL-273
/
Jira
SAK-800
SAK-800

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)
TC6: 

Jira
SAK-17891
SAK-17891

TC7: 
Jira
SAK-18760
SAK-18760

TC7 experiment: http://steveswinsburg.wordpress.com/2011/04/07/sakai-runs-in-tomcat-7/


JDK 1.6

Jira
SAK-20089
SAK-20089

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

Jira
SAK-19282
SAK-19282

Upgrade to jsf 1.1_02

 

Completed-ish (many tools need review)

JSF

Jira
SAK-20086
SAK-20086

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

Jira
SAK-20243
SAK-20243

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

Jira
SAK-20243
SAK-20243

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

Savitha Prakash

Yes

No

- Add announcement API support in Entity Broker (SAK-18764)
- Allow individual announcements to be retrieved the entitybroker
(SAK-20562)

 


Assignments

Zhen Qian


 


 

 

BasicLTI

Charles Severance

 

 

 

 

 

Chat 

Maintenance Team

 

 

 

 

 

Calendar Summary

Maintenance Team


 

 

 


Citations

Jon Dunn


 




Email Archive

Matthew Jones

 

 


 

 

Email template service

David Horwitz

 

 

 

 


Gradebook

Kirk Alexander, Jonathan Cook


 



 

I18n

Beth Kirschner

 

 


 

 

Linktool

Charles Hedrick


 




OSP

Chris Maurer, Noah Botimer

 

 

 

 

 

Podcasts

Tan Nguyen


 




Portal

Matthew Buckett, Charles Severance


 


 


Post'Em

Ying Wang


 



 

Preferences 

Maintenance Team 

 

 

 

 

 

Quartz Scheduler 

Maintenance Team  

 

 


 


Roster 

Maintenance Team  

 

 

 

 

 

Resources, Drop Box

Maintenance Team

 

 


 

 

rWiki

Savitha Prakash


 


 


Syllabus

[~gjthomas]


 



 

Schedule

Beth Kirschner

 

 

 

 

 

Site Info

Zhen Qian

 

 

 

 

 

WebDAV

Charles Hedrick

 

 

 

 


Worksite Setup

Zhen Qian

 

 

 

 

 

WYSIWYG Editor

Noah Botimer

 

 

 

 

 

 

 

 

 

 

 

 

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

David Horwitz


 


 


edu-services

David Horwitz


 



 

Entity Broker

Aaron Zeckoski


 


 

 

hybrid

Lance Speelmon


 


 


 

Kernel

David Horwitz

 

 



Message Center

[~wagnermr]




 


Samigo (Aka Tests & Quizzes)

Lydia Li


 

 

 


Profile2

Steve Swinsburg

Yes

Yes

Abandon SakaiPerson. Reimplement. (PRFL-230)
Allow customisable fields (PRFL-390)
Create worksite based on connections (PRFL-388)
Mutual connections panel (PRFL-124)
Tag your connections (PRFL-104)
Combined/simplified search (w/ filtering) (PRFL-381)
Badges (PRFL-631)

1.5.0


Polls

David Horwitz


 



 

Reset Password 

David Horwitz


 


 

 

purepoms

 

 

 

 

 

 

Search

David Horwitz


 

 


 

Site Stats

Maintenance Team



 


 

Web services

Steve Swinsburg

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:
    Code Block
    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.