2.5 Release Planning-11 (20071128)

Owned by Former user (Deleted)
Last updated: Nov 28, 2007Version comment
2 min read

Attendees

Meeting Agenda

Open Blocker Critical issues: http://bugs.sakaiproject.org/confluence/pages/viewpage.action?spaceKey=QA&title=Pre-Release2.5BranchMgmt&macro.refresh=true#jiraissues

Overview (Standing item)

Timeline Review
  • Nov 7 tag 2.5.0.012
  • Nov 22 2.5.0.beta cut
  • Nov 26 2.5.0.beta deployed to QA network
  • Dec 13 2.5.0.RC1 (Release Candidate 1)
  • Jan 21 2.5.0.RC2 (Release Candidate 2)
  • Feb 12 2.5.0 Release
Goals
  • Elimination of all outstanding Blocker and Critical bugs for 2.5
  • Acceptable Performance testing on mysql and oracle databases for Assignments, Resources, Forums, GB & T&Q. What is acceptable? At this point in time, no degradation from performance experienced in 2.4
  • High degree of verification (85%) of resolved JIRA bugs
  • Confirmed functional testing on all tools.
  • Positive feedback from sites running a tagged version of off branch.

Where we stand

Issues Reported against just 2.5

2.5.0.013

2.5.0.beta

2.5.0.rc1

2.5.0.rc2

Blocker

4

3

 

 

Critical

20

14

 

 

Total

24

17

 

 

2.5.0.beta Blockers - one documentation, two recently opened

2.5.0 Beta Critical -  There are 3 that we do not have anyone working on (SAK-10487, SAK-11798, SAK-12056).  One of those is related to performance in Forums as well as another that was unassigned. 6 reported in the  last 2 weeks.

All Outstanding tickets (just bugs, no tasks)

2.5.0.013

2.5.0.beta

2.5.0.rc1

2.5.0.rc2

Blocker

3

3

 

 

Critical

58

55

 

 

Total

61

58

 

 

Changes in 2.5.0.Beta
34 tickets - as with the .13 tag, most with Assignments

Progression

Q: How do we move from Beta? RC?
A: To make the progression from beta to release candidate, the aim is the resolution of outstanding blocker and critical bugs reported.

Q: Are we going to make the move from Beta to RC?
There are a number of critical issues reported against a 2.5 build we're not likely to get movement on due to resources being unavailable. What do we do with these problems?