Child pages
  • Sakai 2.6.2 and 2.5.6 Jira Candidates

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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

Review Meeting Decision 2009-12-08

Matthew Jones

Jira
SAK-16963
SAK-16963

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

Noah Botimer

Jira
SAK-16863
SAK-16863

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

Jira
SAK-17204
SAK-17204

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

 

Jira
SAK-17048
SAK-17048

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

Jira
SAK-14351
SAK-14351

/

Jira
KNL-306
KNL-306

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

 

Jira
SAK-13693
SAK-13693

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

 

Jira
SAK-13675
SAK-13675

/

Jira
KNL-307
KNL-307

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)

 

Jira
SAK-14261
SAK-14261

/

Jira
KNL-257
KNL-257

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

Jira
KNL-270
KNL-270
may be too much per messages on sakai-dev

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

 

Jira
SAK-16838
SAK-16838

/

Jira
KNL-325
KNL-325

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

 

Jira
SAK-13532
SAK-13532

/

Jira
KNL-213
KNL-213

see 2.5.6 below

depends on status of KNL-213 in K1 1.0.13

 

Jira
SAK-17536
SAK-17536

fixes a possible regression

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

Seth Theriault

Jira
SAK-15657
SAK-15657

/

Jira
KNL-327
KNL-327

and

Jira
SAK-15571
SAK-15571

(see 2.5.6)

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

 

Jira
SAK-16304
SAK-16304

and

Jira
SAK-16303
SAK-16303

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

 

Jira
SAK-17430
SAK-17430

merged into 2.6.x branch

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

 

Jira
SAK-17414
SAK-17414

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

Jira
KNL-261
KNL-261

and

Jira
KNL-263
KNL-263

related to

Jira
SAK-12705
SAK-12705

(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

 

Jira
SAK-17512
SAK-17512

merged to 2.6.x at r69681 by Beth K.

NOT REVIEWED

Sakai 2.5.6

Release date: 1st week Dec. 2009

Proposer

Candidate

Comments

Review Meeting Decision 2009-12-08

Seth Theriault

Jira
SAK-13714
SAK-13714

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

 

Jira
SAK-14351
SAK-14351

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

 

Jira
SAK-13693
SAK-13693

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

 

Jira
SAK-13675
SAK-13675

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

 

Jira
SAK-14261
SAK-14261

will run at Columbia in January 2010. It's already fixed in

Jira
KNL-257
KNL-257

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

 

Jira
SAK-12551
SAK-12551

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

 

Jira
SAK-16838
SAK-16838

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

Jira
KNL-325
KNL-325

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

 

Jira
SAK-13532
SAK-13532

is also on the list for local testing, but problems noted in

Jira
KNL-213
KNL-213

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

 

Jira
SAK-12536
SAK-12536

fixed in 2.6.0 release, merged into 2.5.x branch

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

 

Jira
SAK-11377
SAK-11377

fixed in 2.6.0 release, merged into 2.5.x branch

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

 

Jira
SAK-15657
SAK-15657

and

Jira
SAK-15571
SAK-15571

both have fixes in JIRA for 2.5.x.

Jira
SAK-15657
SAK-15657

was committed to K1 trunk on 15-Nov-2009 and

Jira
SAK-15571
SAK-15571

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

 

Jira
SAK-16304
SAK-16304

and

Jira
SAK-16303
SAK-16303

ran in 2.5 at Oxford (testing at Columbia for January 2010)
NOTE: Columbia is using a consolidated patch for

Jira
SAK-16304
SAK-16304
and

Jira
SAK-16303
SAK-16303

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

 

Jira
SAK-17430
SAK-17430

tested at Columbia; merged into 2.5.x branch

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

 

Jira
SAK-13127
SAK-13127

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

Jira
SAK-17204
SAK-17204

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

 

Jira
SAK-13672
SAK-13672

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

Jira
SAK-14390
SAK-14390

Jira
SAK-7209
SAK-7209
(new feature)
Jira
SAK-14385
SAK-14385

Jira
SAK-12523
SAK-12523

Jira
SAK-13390
SAK-13390

Jira
SAK-16628
SAK-16628

the original merge request was for

Jira
SAK-14390
SAK-14390

, 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)

 

Jira
SAK-12705
SAK-12705

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