| Section |
|---|
| Column |
|---|
We are working on the release of RAFT II. This is a major release. This checklist tracks is the current release path of RAFT II to the service operations, primarily from the Business Intelligence development team to Customer Support, Training, and Server & System Administration. Change Management - Enter release date, and other significant dates, on Change Communications Calendar.
- Exchange resource name: IS&T: Change Communications
- When these dates change, communicate to ist-pipeline list.
- This has not been done in a while, dates have changed a lot.
- Planned major milestones recorded on wiki home page
|
|
This documentation is for planning the release of RAFT PhII to the support areas of IS&T. Other parts of the project plan and implementation details that are not relevant to support teams should go elsewhere.
Checklist
Not in order of priority or chronology yet.
From Resources
- Enter release date on Change Communications Calendar or email dates to release-core@mit.edu.
- If you require a custom installer, complete SWRT's Installer Support Request Form at least two week prior to release.
- Complete Release-Decision Template.
- Form release team.
From Impact (including high-impact items though this project really doesn't rate)
...
- .
- Send announcement and change log to
|
|
...
...
- pipeline@mit.edu, stakeholder list once release is complete.
- Update any known open issues (Jira, Request Tracker) affected by release and close.
- Search http://ist.mit.edu.ezproxyberklee.flo.org and http://kb.mit.edufor any articles that would be invalidated by release and update as needed. Contact istweb@mit.edu if you are not sure how to update this documentation.
- Contact IS&T Communications for public release announcement.
- If sending outside of IS&T, send draft release announcement to IS&T communications team at least 2 business days prior to release.
|
|
...
- Inform ist-pipeline@mit.edu, pipeline of release at least 1 business day prior to release.
- Consider how to support early adopters or pilot users, phase out current version?
- Pilot release in May, community release in June. Still no hard transition plan for RAFT I users?
- Review need to de-support of previous version(s)
|
|
...
- , communications to current users.
- Create communication plan, based on stakeholders identified in prior steps.
Configuration Management - Critical Path: Need stable test environment!
- Migrating from RAFT I environments to new, clean VMs for RAFT II
- raft-test in place, needs PHP downgrade?
- raft-r1, new raft production, does not exist yet.
- Await decision on budget for drupal-based online help systems. bi-help-dev installed on temporary system so documenation staff can begin work.
- Update datacenter SLAs with technical, financial, business contact information.
Release and Deployment Management - OLA: business-support team engagement, OLA in development: Service Levels Development
- Developing blanket OLA between business-support and Business Intelligence team.
- Code management/versioning and continuous integration plan with release engineer. Deploy from Bamboo or directly from SVN.
Evaluation and Testing - See "evaluators" list at right. Responsible parties for internal evaluation. Must sign off. Second architecture review still required by this group.
- Input and sign-off by Usability Team: Usability & Accessibility Reports.
- Stakeholder committee schedule in place, core business users signed up for rolling usability-test plan.
- BI Team to provide smoke-test/system health page for Customer Support?
- business-help and business-intelligence teams to perform smoke tests for every patch or update during burn-in period (six week from go-live).
Knowledge Management - Training Plan
- Training mutual venture of SE Training team and COUES Training team.
- Training curriculum, work with Training to ramp-up Help Desk (business-support).
- Online Help: SE Training, Mark Wiklund.
- Develop RAFT escalation scripts from Tier 2 (business-support) and Tier 3 (raft-support). Support Escalations Outline
|
| Column |
|---|
| Panel |
|---|
| borderColor | blue |
|---|
| borderWidth | 1 |
|---|
| title | Transition Teams |
|---|
| borderStyle | solid |
|---|
| When in doubt, raft-support@mit.edu. Release Team
Technical Lead, Amon Horne
Release Coordination, Steve Landry
Systems Operations, Nathan Thaler
COEUS Integration: Carol Wood Evaluation, Internal Acceptance
Accessibility and Usability: Katherine Wahl
Database Administration Team: Rob Grenier
Service Desk: Jessica Donnelly Reed
Server and Systems Administration: Garry Zacheiss
Business-user testing team, mitbi-test@mit.edu Knowledge Management
Jessica Donnelly Reed: Service Desk
Mark Wiklund: Training
Peggy McGrath: Business Intelligence
Carole Trainor: COUES Training |
|
|
From Risk
- Search http://ist.mit.eduand
Image Removed http://kb.mit.eduforImage Removed any articles that would be invalidated by release and update as needed. Contact istweb@mit.edu if you are not sure how to update this documentation. - If posting new software, contact the Software Release Team to ensure that previous and new versions are archived in their definitive software library.
- Test software on all supported operating systems.
- Create testing plan.
Notes
We are a pilot for IS&T's product-release checklist. We used it as a base for this plan though it was developed for distributed/desktop release. Notes for Release-Core.
Product-Release Checklist. You might not have authorizations to view the release-core wiki.
...