This shows the timeline for each release. A template exists which will be more useful for checking items off.
Pre-release
- Verify release with dev + QA team (RK)
- Update product (RK)
- Version number, FCKsource
- Verify database updates work
- Compile release notes (RK)
- Outline breaking changes:
- New writeable resources
- Apache conf changes
- New directories
- New packages and dependencies
- Create filter for resolved bugs in Mantis
- Create filter for resolved features in Mantis
- Write a summary of release
- Update all closed/resolved bugs set to "future" target release to current target release
- Move all open bugs from current target release to next target release or "future"
- Run Daniil's unit tests and ensure they pass on the stable branch (MM)
- Update development multi-tenants to release (PE)
- Post RC1 to SourceForge (PE)
- Merge localization changes from translate dialog (GS)
- Enterprise module testing (RM)
- Confirm Modules can be installed
- SQL
- SalesForce
- SugarCRM
- Access
- SnapLogic
- VisiFire
- Use Template to verify that the modules can query - need to have templates to verify functionality
- Needs to be tested on VMware and a Windows Deployment
- MSI-specific scenarios
Basic Cases: - Clean install Win2k3
- Clean install Vista
- Upgrade Win2k3
- Upgrade Vista
Environmental conditions that affect setup: - Is LUA enabled?
- Has the wiki been configured?
- Is the computer using Active Directory?
- Are any of these already installed: IIS, FastCGI, PHP, ImageMagick?
Release day
- Compile release binaries (PE)
- Update README from release notes (PE)
- Create release branch (only for major) (PE)
- Post open-source tarball on SF (PE)
- Merge release into VM branch (PE)
- Sync SourceForge.net SVN (PE)
- Prep .vmdk, .vmx for VMware image (MO)
- Post open-source VM on SF (MO)
- Test upgrade and fresh install (RM)
- Verify upgrade from open-source to community works (RM)
- Post enterprise VM on SF and S3 (MO)
- Test inactive -> trial -> community upgrade (RM)
- Give copy to RM for posting to VMware marketplace (RK)
- Update /s/enterprise.php (RK)
- Give S3 link to Irene
- Post Win2K3 enterprise MSI on SF and S3 (MO)
- Test inactive -> trial -> community upgrade (RM)
- Give S3 link to Irene
- Post Vista/Win2K8 enterprise MSI on SF and S3 (MO)
- Test inactive -> trial -> community upgrade (RM)
- Give S3 link to Irene
- Post open source RPMs (MO)
- Test inactive -> trial -> community upgrade (RM)
- Post enterprise RPMs
- Test inactive -> trial -> community upgrade (RM)
- Update release notes with all links and SVN numbers (RK)
- Update developer download page
- Update website download links (needs S3 links for each)
- Update website verbiage to reference appropriate version and correct S3 download link ( IV )
After release
- Update upgrade install guides for main website (RM)
Check install guide styles ( IV ) - Update version pinging site (updates.mindtouch.com) (RK)
- Post blog post, announce in forums (RK)
- Update Mantis with next release (RK)
- Update community install guides (RM)
- We need to reorganize the community documentation as of Oct '08 post links here once documentation is cleaned up on wiki.dev.mt