Sakai 2.6.2 and 2.5.6 Jira Candidates

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

SAK-14351 - Getting issue details... STATUS / KNL-306 - Getting issue details... STATUS

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)

SAK-13675 - Getting issue details... STATUS / KNL-307 - Getting issue details... STATUS

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

SAK-14261 - Getting issue details... STATUS / KNL-257 - Getting issue details... STATUS

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

SAK-16838 - Getting issue details... STATUS / KNL-325 - Getting issue details... STATUS

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

Seth Theriault

SAK-15657 - Getting issue details... STATUS / KNL-327 - Getting issue details... STATUS and SAK-15571 - Getting issue details... STATUS

(see 2.5.6)

ran in 2.5 at Oxford (see 2.5.6)

ran in 2.5 at Oxford (see 2.5.6)

on 2.6.x merge list

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

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 KNL-257 - Getting issue details... STATUS 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

has a fix in JIRA for 2.5.2, although 2.5 is not on the affected versions list. It's already fixed in KNL-325 - Getting issue details... STATUS 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 KNL-213 - Getting issue details... STATUS 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, recently merged into 2.5.x branch

fixed in 2.6.0 release, recently merged into 2.5.x branch

SAK-15657 - Getting issue details... STATUS and SAK-15571 - Getting issue details... STATUS

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

ran in 2.5 at Oxford (testing at Columbia for January 2010)
NOTE: Columbia is using a consolidated patch for SAK-16303 - Getting issue details... STATUS and SAK-16304 - Getting issue details... STATUS

ran in 2.5 at Oxford (testing at Columbia for January 2010)
NOTE: Columbia is using a consolidated patch for SAK-16303 - Getting issue details... STATUS and SAK-16304 - Getting issue details... STATUS

tested at Columbia; on 2.5.x merge list

running in production at Columbia since August 2009; already fixed in 2.6.0