MindTouch Developer Center > Deki > Release Timeline

Release Timeline

Table of contents
  1. 1. Pre-release
  2. 2. Release day
  3. 3. After release

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)
    • Announce in forums (RK)
  • Merge localization changes from translate dialog (GS)
  • Enterprise module testing (RM)
    1. Confirm Modules can be installed
      1. SQL
      2. SalesForce
      3. SugarCRM
      4. Access
      5. SnapLogic
      6. VisiFire
    2. Use Template to verify that the modules can query - need to have templates to verify functionality
    3. Needs to be tested on VMware and a Windows Deployment
  • MSI-specific scenarios
    Basic Cases:
    1. Clean install Win2k3
    2. Clean install Vista
    3. Upgrade Win2k3
    4. Upgrade Vista
  • Environmental conditions that affect setup:
    1. Is LUA enabled?
    2. Has the wiki been configured?
    3. Is the computer using Active Directory?
    4. 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

 

Tag page
You must login to post a comment.
Powered by MindTouch Deki v.8.08.1a