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.

...

Proposer

Candidate

Comments

Noah Botimer

Jira
SAK-16863
SAK-16863

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

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

 

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"

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)

 

Jira
SAK-13693
SAK-13693

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

 

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)

 

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)

 

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

Seth Theriault

Jira
SAK-15657
SAK-15657
/
Jira
KNL-327
KNL-327
and
Jira
SAK-15571
SAK-15571

(see 2.5.6)

 

Jira
SAK-16303
SAK-16303

ran in 2.5 at Oxford (see 2.5.6)

 

Jira
SAK-16304
SAK-16304

ran in 2.5 at Oxford (see 2.5.6)

 

Jira
SAK-17430
SAK-17430

on 2.6.x merge list

Sakai 2.5.6

Release date: 1st week Dec. 2009

Proposer

Candidate

Comments

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

 

Jira
SAK-14351
SAK-14351

ran in 2.5 at Oxford (testing at Columbia for January 2010)
JFL: +1 if tests are fine

 

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

 

Jira
SAK-13675
SAK-13675

longstanding bug for 2.5.x (testing at Columbia for January 2010)
JFL: +1 if tests are fine

 

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

 

Jira
SAK-12551
SAK-12551

is possible (testing at Columbia for January 2010)
JFL: +1 if tests are fine

 

Jira
SAK-16838
SAK-16838

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

 

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

 

Jira
SAK-12536
SAK-12536

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

 

Jira
SAK-11377
SAK-11377

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

 

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

 

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-16303
SAK-16303
and
Jira
SAK-16304
SAK-16304

 

Jira
SAK-16304
SAK-16304

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

Jira
SAK-16303
SAK-16303
and
Jira
SAK-16304
SAK-16304

 

Jira
SAK-17430
SAK-17430

tested at Columbia; on 2.5.x merge list