Sakai 2.6.2 and 2.5.6 Jira Candidates

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

Proposer	Candidate	Comments	Review Meeting Decision 2009-12-08
Matthew Jones	SAK-16963 - Getting issue details... STATUS	MJ: Merged to 2.6.x at 69734 12/11. Run at Michigan in production since September. Needed for mneme.
Noah Botimer	SAK-16863 - Getting issue details... STATUS	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	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 2009-12-09: Merged to 2.6.x at r69609	+1 to 2.6.x merge +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 2.6.x merge -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 2.6.x merge +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 2.6.x merge +1 to 2.6.2 release
	SAK-13675 - 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 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 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