This an active list of JIRA issues under consideration for inclusion in Sakai 2.6.2 and 2.5.6.

For a list of relevant JIRA filters, see http://confluence.sakaiproject.org/display/REL/Jira+Issue+filters+%282.6%2C+2.5%29

Sakai 2.6.2

Release date: 1st week Dec. 2009

Proposer

Candidate

Comments

Noah Botimer

JFL: isn't it already merged into 2.6.x, see 09-Nov-2009

Adam Marshall

This is causing us big problems - lots of people print out the schedule and distribute it and now all the times are wrong so they cant do this anymore.
JFL: I think it's critical, not just major

 

We've also had complaints about this issue (to a lesser degree).
JFL: brings again the question of who is maintaining Portal, at least Megan is lead on "View As"

Jean-François Lévêque

/

no reason to keep it out of 2.6 if it gets into 2.5 (see 2.5.6)

 

no reason to keep it out of 2.6 if it gets into 2.5 (see 2.5.6)

 

/

no reason to keep it out of 2.6 if it gets into 2.5 (see 2.5.6)

 

/

no reason to keep it out of 2.6 if it gets into 2.5 (see 2.5.6)

 

/

no reason to keep it out of 2.6 if it gets into 2.5 (see 2.5.6)
SLT: requires a new K1 1.0.x build for inclusion
Involves an API change and may not be appropriate for maintenance release

Seth Theriault

/ and

(see 2.5.6)

 

and

ran in 2.5 at Oxford (see 2.5.6)

 

merged into 2.6.x branch

 

on 2.6.x merge list (messages on sakai-dev seems to indicate patch works)

Sakai 2.5.6

Release date: 1st week Dec. 2009

Proposer

Candidate

Comments

Seth Theriault

fixes a problem in 2.5.x (testing at Columbia for January 2010)
JFL: +1 if tests are fine
SLT: looks OK; on 2.5.x merge list

 

ran in 2.5 at Oxford (testing at Columbia for January 2010)
JFL: +1 if tests are fine
SLT: looks OK; should be put on 2.5.x merge list

 

ran in 2.5 at Oxford (testing at Columbia for January 2010). Not sure if how complicated it is for 2.5.
JFL: +1 if tests are fine
SLT: looks OK; should be put on 2.5.x merge list

 

longstanding bug for 2.5.x (testing at Columbia for January 2010)
JFL: +1 if tests are fine
SLT: looks OK; should be put on 2.5.x merge list

 

will run at Columbia in January 2010. It's already fixed in and included in the K1 1.1 beta.
JFL: +1 if tests are fine
SLT: looks OK; on 2.5.x merge list

 

is possible (testing at Columbia for January 2010)
JFL: +1 if tests are fine
SLT: looks OK; on 2.5.x merge list

 

Involves an API change and may not be appropriate for maintenance release
has a fix in JIRA for 2.5.2, although 2.5 is not on the affected versions list. It's already fixed in and included in the K1 1.1 beta; would require a new K1 1.0.x build.
JFL: +1 if tests are fine
SLT: testing at Columbia for January 2010

 

is also on the list for local testing, but problems noted in are making me jumpy.
JFL: -1 until we have good news from kernel, +1 and merge also into 2.6 if we have good news
SLT: Removed from Columbia build

 

fixed in 2.6.0 release, merged into 2.5.x branch

 

fixed in 2.6.0 release, merged into 2.5.x branch

 

and

both have fixes in JIRA for 2.5.x. was committed to K1 trunk on 15-Nov-2009 and has been on the 2.5.x merge list since April 2009
SLT: testing at Columbia for January 2010

 

and

ran in 2.5 at Oxford (testing at Columbia for January 2010)
NOTE: Columbia is using a consolidated patch for and for simplicity because of patch dependencies

 

tested at Columbia; merged into 2.5.x branch

 

running in production at Columbia since August 2009; already merged in 2.6.0
Joshua Swink, UC Merced: Not fixed in 2.6.0 (via Jira)

Zhen Qian


(new feature)



the original merge request was for , but it requires the others to work; all merged into 2.5.x branch
SLT: As of 2009-12-07, these changes make 2.5.x unusable

Adam Marshall

see 2.6.2 above
BK (via Jira): Affects 2.5.x as well
SLT: testing at Columbia for January 2010