2.4 Release

2.4 release

Please checkback often or watch the page throughout the 2.4 release

TOC

• Release Schedule
• Release Planning Meeting Information
• Fixes for the next tag
• Information & Resources
• Participation Sign up
• What is preliminary testing and how do I participate?

• Testing status and comments

Tentative Testing Schedule

Release Planning Meeting Information

A video bridge has been set up so attendees can connect via Polycom or by phone.
Weekly: Every Wed from 12-1:30pm Eastern

Daily Count Down:  May 12-May 21 11am Easternhttp://bugs.sakaiproject.org/confluence/display/QA/Meetings+and+notes

Please see Connection information and Meeting Notes

Helpful Information

• Test Servers
• Test Conditions and Scripts

• What's in 2.4?
  • Special Sakai.Properties for 2.4
  • QA Issues Awaiting Verification
• Meeting Notes

• QA FAQ
• How to Guide to How tos including adding stealthed tools, opening/closing JIRA's ect
• The Email Archive for this Working Group can be found on the Collab Sakai WG: QA site. (Note that you need separate accounts for accessing Collab and Confluence/Jira.)
• JIRA, Bug Tracking System
• Installation Documentation Staging area

2.4 QA Participation Signup

What is preliminary testing and how do I participate?

Note: The Preliminary Testing Phase is over

Preliminary testing is an initiative new to the 2.4 release process. In past release cycles, the code has undergone a larger amount of change once the "code freeze" occurred due to discovered regressions and unexpected bugs resulting from functionality changes. Prior to the 2.3 release a group of individuals in the community spent time working closely with the Resources development team and completed a few cycles of testing on new functionality that greatly assisted in making the 2.3 release much smoother. This shall be a model the QA WG will work with in order to complete a few cycles performing focused testing on select parts of the application. Not only will this allow us to speak more confidently to the quality and stability of the code, but will also help foster better collaboration between the development and quality assurance work groups.

How will I know what to test?
Development team leads will receive email 3 business days prior to a new tag requesting that they indicate if their component is ready for testing. For this reason testing should only occur on areas where leads have communicated that QA has the green flag to test to ensure that resources are directed where they are needed most. Fixes and functionality will be listed in the following JIRA filter: [Filter removed]

Components to test will be sent out to the QA WG as well as posted here:
2.4.0.001 tag

• Message Center, Podcasts, Post'Em, Privacy, Profile, Syllabus, and Web Content
• OSP: all tools with a focus on goal mgmt (this tool is on the OSP QA-2 server)

2.4.0.002 tag

• Wiki, Podcasts, Post'Em, Privacy, Profile, Syllabus, and Web Content
• OSP: all tools with a focus on goal mgmt (this tool is on the OSP QA-2 server)

2.4.0.003

• Assignments (everything but SAK-8589/assignment upload all), Gradebook, Post'Em, Profile, Roster, Syllabus, Web Content, StyleAble, PreferAble
• please note the file picker is broken so please avoid testing attachment functionality

How will I know where to test?
All test servers and their current status can be located on the Test Instance Confluence space

Should I close bugs?
Yes, please perform verification as you would during the official QA cycle. Please remember to note the servers and tag you verified a fix against.