Child pages
  • Sakai 2.6.2 and 2.5.6 Jira Candidates
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

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

Noah Botimer

SAK-16863 - Getting issue details... STATUS

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

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

Adam Marshall

SAK-17204 - Getting issue details... STATUS

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

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

 

SAK-17048 - Getting issue details... STATUS

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 merge to 2.6.x
-1 to 2.6.2 release
(need maint team)

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)

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

 

SAK-13693 - Getting issue details... STATUS

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

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

 

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)

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

 

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)

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

 

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
Involves an API change and may not be appropriate for maintenance release

 

SAK-17536 - Getting issue details... STATUS

fixes a possible regression

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

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)

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

 

SAK-16304 - Getting issue details... STATUS and
SAK-16303 - Getting issue details... STATUS

ran in 2.5 at Oxford (see 2.5.6)

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

 

SAK-17430 - Getting issue details... STATUS

merged into 2.6.x branch

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

 

SAK-17414 - Getting issue details... STATUS

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

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

Sakai 2.5.6

Release date: 1st week Dec. 2009

Proposer

Candidate

Comments

Review Meeting Decision 2009-12-08

Seth Theriault

SAK-13714 - Getting issue details... STATUS

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

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

 

SAK-14351 - Getting issue details... STATUS

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 merge to 2.5.x
+1 to 2.5.6 release

 

SAK-13693 - Getting issue details... STATUS

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 merge to 2.5.x
+1 to 2.5.6 release

 

SAK-13675 - Getting issue details... STATUS

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 merge to 2.5.x
+1 to 2.5.6 release

 

SAK-14261 - Getting issue details... STATUS

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

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

 

SAK-12551 - Getting issue details... STATUS

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 merge to 2.5.x
+1 to 2.5.6 release

 

SAK-16838 - Getting issue details... STATUS

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

 

 

SAK-13532 - Getting issue details... STATUS

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

 

 

SAK-12536 - Getting issue details... STATUS

fixed in 2.6.0 release, merged into 2.5.x branch

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

 

SAK-11377 - Getting issue details... STATUS

fixed in 2.6.0 release, merged into 2.5.x branch

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

 

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

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

 

SAK-16304 - Getting issue details... STATUS and
SAK-16303 - 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-16304 - Getting issue details... STATUS and SAK-16303 - Getting issue details... STATUS for simplicity because of patch dependencies

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

 

SAK-17430 - Getting issue details... STATUS

tested at Columbia; merged into 2.5.x branch

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

 

SAK-13127 - Getting issue details... STATUS

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)

 

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
SAK-16628 - Getting issue details... STATUS

the original merge request was for SAK-14390 - Getting issue details... STATUS , 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)

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

Adam Marshall

SAK-17204 - Getting issue details... STATUS

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

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

 

SAK-13672 - Getting issue details... STATUS

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

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

  • No labels