Sakai 2.6
...
| Anchor | ||||
|---|---|---|---|---|
|
QA Reporting Lexicon (new)
I would like to suggest adopting a standard lexicon of QA terms to be used in jiras and when report results. The following are suggested terminology and definitions:
- QA SUMMARY - summary of testing plan, OS tested, instance tested on, browser, etc.
- QA RESULTS - detailed results on the testing
- QA UFO - Unexpected Functional Oddity: strange anomalies that are not bugs, but perhaps should be addressed or investigated
- QA VERIFIED - Issues is verified and passes QA, comments
- QA UNVERIFIED --could not verify because it is not testable or failed QA, comments
Release Schedule
Updated: 23-Apr-2009
The release team reserves the right to adjust deadlines, in order to produce a quality release, and to accommodate holidays, weekends, etc.
| Event | Weeks | Target | Description | Responsibility |
|---|---|---|---|---|---|
| Call for Tool Promotions | 23 | 11-Aug-2008 | Put call out call for nominations of tools to be promoted/demoted in the release. | Project Coordinator |
| Kernel API Freeze | 22 | 15-Aug-2008 | Freeze Kernel API's. | Kernel Team |
| Feature Freeze | 21 | Preliminary tool and service change specifications should be shared for work intended for the next release. A complete specification for the project should be made available in the project's Confluence space, and a summary should be incorporated into the Sakai Roadmap. | Project Teams | |
| Specification Freeze | 20 | 07-Sep-2008 | Project specifications are frozen. Summaries and full specifications of what is changing should be re-published in their updated form, including for projects seeking tool status changes. | Project Teams |
| Tool Promotion Deadline | 20 | 07-Sep-2008 | End of nominations for tool status changes. Discussion of tool promotion can begin prior to this, but all should be underway by this time. | Community |
| Kernel Freeze | 19 | 07-Sep-2008 | Freeze K1 kernel in preparation for Sakai 2.6 | Kernel committers |
| Upgrade Freeze | 18 | 15-Sep-2008 | Upgrades and additions to shared/common jar files and tools (e.g., java, maven, dbcp, spring, hibernate, tomcat) are completed. | Project Teams |
| Tool Status Freeze | 18 | 15-Sep-2008 | Decisions are finalized on promoting and retiring tools. Project teams begin work related to status changes. | Community |
| Code Freeze | 16 | All changes to code completed, including sakai.properties settings, appropriate default permissions, work related to tool status changes, database upgrade/conversion scripts, help documentation, etc. Begin determining what features are incomplete and removing them from the release in time for the Test Freeze. | Project Teams | |
| Test Freeze | 15 | 06-Oct-2008 | Complete the removal of unfinished features. Final specifications are published in full and summary forms. Formal QA begins; informal QA, such as verifying Jira's, is likely to have been going on for awhile prior to this. Generally only bug fixes are allowed past this point. | Project Teams |
| Branch Freeze | 10 | 06-Oct-2008 | 2.6 branch for release is cut from trunk. Changes after this point will require merging from trunk to the release branch by Branch Managers. | Branch Manager |
| Alpha tags | 15 | 06-Oct-2008 | Begin tagging alpha (QA) releases. | Branch Manager |
| Beta tags | 10 |
| Begin tagging beta releases. | Branch Manager |
| Beta01 | 8 | 02-Feb-2009 | Released | Branch Manager |
| Beta02 | 7 | 20-Feb-2009 | Released | Branch Manager |
| Beta03 | 5 | 01-Mar-2009 | Released |
|
| String Freeze | 3 | 16-Jan-2009 | No more changes in UI text, so the Internationalization WG can create translations and the Help WG can update documentation. Implementors can also begin updating their local documentation. (If you're tool will be ready prior to String Freeze, please let the community know, so that work can get started early on translations and help documentation. See Sakai 2.6 Translations.) | Project Teams |
| Release Candidates | 3 | 21-Apr-2009 | Begin tagging release candidates. | Branch Manager |
| RC01 | 2 | 22-Apr-2009 | Release candidate tag is cut, distributed to QA server admins for installation, and made available for early adopters. | Branch Manager |
| QA RC Testing | 2 | 22-Apr-2009 | Regression and adhock testing of RC releases | QA WG |
| RC02 | 1 | 01-May-2009 | Release candidate tag is cut, distributed to QA server admins for installation, and made available for early adopters. | Branch Manager |
| Release Documentation | 1 | 05-May-2009 | Create, vett and publish documentation for the 2.6.0 release. | Release Management WG |
| RC03 | 1 | 07-May-2009 | Release candidate tag is cut, distributed to QA server admins for installation, and made available for early adopters. | Branch Manager |
| RC04 | 1 | 22-May-2009 | Release candidate tag is cut, distributed to QA server admins for installation, and made available for early adopters. | Branch Manager |
| RC05 | 1 | 15-June-2009 | Release candidate tag is cut, distributed to QA server admins for installation, and made available for early adopters. | Branch Manager |
| RC06 | 1 | 30-June-2009 | Release candidate tag is cut, distributed to QA server admins for installation, and made available for early adopters. | Branch Manager |
| Official | 0 | Software is officially released. | Everyone |
Low response rate. There will be no published catalog of tool or service specifications for 2.6. 
...