Sakai 2.6.2 and 2.5.6 Jira Candidates

Matthew Jones

MJ: Merged to 2.6.x at 69734 12/11. Run at Michigan in production since September. Needed for mneme.

Noah Botimer

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

+1 to 2.6.x merge
+1 to 2.6.2 release

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
2009-12-09: Merged to 2.6.x at r69609

+1 to 2.6.x merge
+1 to 2.6.2 release

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"

+1 to 2.6.x merge
-1 to 2.6.2 release
(need maint team)

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)

+1 to 2.6.x merge
+1 to 2.6.2 release

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

+1 to 2.6.x merge
+1 to 2.6.2 release

/

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

+1 to 2.6.x merge
+1 to 2.6.2 release
(pending Kernel review)

/

no reason to keep it out of 2.6 if it gets into 2.5 (see 2.5.6)
2009-12-09: may require commits for all tasks under
KNL-270 - Getting issue details... STATUS may be too much per messages on sakai-dev

+1 to 2.6.x merge
+1 to 2.6.2 release
(pending Kernel review)

/

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

-1 to 2.6.x merge
-1 to 2.6.2 release
Mention in 2.6.2 Rel Notes

/

see 2.5.6 below

depends on status of KNL-213 in K1 1.0.13

fixes a possible regression

+1 to 2.6.x merge
+1 to 2.6.2 release
(pending followup?)

Seth Theriault

/

and

(see 2.5.6)

+1 to 2.6.x merge
+1 to 2.6.2 release

and

ran in 2.5 at Oxford (see 2.5.6)
2009-12-09: Both merged to 2.6.x at r69612

+1 to 2.6.x merge
+1 to 2.6.2 release

merged into 2.6.x branch

+1 to 2.6.x merge
+1 to 2.6.2 release

on 2.6.x merge list (messages on sakai-dev seem to indicate patch might work)

+1 to 2.6.x merge
+1 to 2.6.2 release
(pending fix confirmation)

From Jira

and

related to

(see 2.5.6)
JIRA reports success with KNL-263; KNL-261 may be moot
SLT: mail out to sakai-dev and production

NOT REVIEWED

merged to 2.6.x at r69681 by Beth K.

NOT REVIEWED

Seth Theriault

fixes a problem in 2.5.x (testing at Columbia for January 2010)
JFL: +1 if tests are fine
SLT: looks OK
2009-12-09: Merged to 2.5.x at r69614

+1 to 2.5.x merge
+1 to 2.5.6 release

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

+1 to 2.5.x merge
+1 to 2.5.6 release

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

+1 to 2.5.x merge
+1 to 2.5.6 release

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

+1 to 2.5.x merge
+1 to 2.5.6 release

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

+1 to 2.5.x merge
+1 to 2.5.6 release

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

+1 to 2.5.x merge
+1 to 2.5.6 release

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

-1 to 2.5.x merge
-1 to 2.5.6 release
Highlight in 2.5.6 Rel Notes
possible for future 2.5 release

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

-1 to 2.5.x merge
-1 to 2.5.6 release

fixed in 2.6.0 release, merged into 2.5.x branch

+1 to 2.5.x merge
+1 to 2.5.6 release

fixed in 2.6.0 release, merged into 2.5.x branch

+1 to 2.5.x merge
+1 to 2.5.6 release

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
2009-12-09: Both merged to 2.5.x at r69618

+1 to 2.5.x merge
+1 to 2.5.6 release

and

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

for simplicity because of patch dependencies
2009-12-09: Both merged to 2.5.x at r69613

+1 to 2.5.x merge
+1 to 2.5.6 release

tested at Columbia; merged into 2.5.x branch

+1 to 2.5.x merge
+1 to 2.5.6 release

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)
SLT: no ill effects at Columbia, but no improvement seen either

need further opinion even if not harmful

Adam Marshall

see 2.6.2 above
BK (via Jira): Affects 2.5.x as well
SLT: testing at Columbia for January 2010
2009-12-09: Merged to 2.5.x at r69611

+1 to 2.5.x merge
+1 to 2.5.6 release

changes were once committed to 2.5.x, but then reverted.

-1 to 2.5.x merge
-1 to 2.5.6 release
(needs further review)

From Jira

SAK-14390 - Getting issue details... STATUS
SAK-7209 - Getting issue details... STATUS (new feature)
SAK-14385 - Getting issue details... STATUS
SAK-12523 - Getting issue details... STATUS
SAK-13390 - Getting issue details... STATUS

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
Zhen Qian concurs with decision to revert (2009-12-08)
2009-12-09: All changes reverted as of r69632

-1 to 2.5.x merge
-1 to 2.5.6 release
(revert all merges)

may be fixed 2.6.0 release (see above), on 2.5.x merge list
SLT: mail out to sakai-dev and production

NOT REVIEWED