Labs/Release

From MozillaWiki
Jump to navigation Jump to search

Overview

Smooth, consistent, and reliable rollout of test and final releases is the best way to get the maximum exposure of the releases and the maximum feedback that will lead to building momentum, mindshare, and marketshare.

Here are the key elements that need to be addressed to ensure smooth rollout of releases.

Configuration Management

Ensure sources are tagged and steps for reproducing the contents of the release are documented and available to others. Myk has some examples here: https://wiki.mozilla.org/Labs/Personas/Build

Testing and Evaluation

  • Examine which areas have been changed since the last release and need testing and evaluation.
  • Evaluate if quality is sufficient each each of the changed areas to ensure beta testers will be able to provide the best feedback.
  • For major releases, establishing a release criteria for areas of the product will help ensure to set the right expectations for all participants in the testing and release activity.
  • performance
  • memory use
  • compatibility
    • backward, forward, cross compatibility with other key products or components
  • security and privacy
  • the right set of expected features,
  • localization, and platform support

Announcement Check List

Keys in this area are to maximize consist release of information and optimize First task of final preparation might be creation of release release notes that contain a summary of:

  • what's working?
  • what's not?
  • what to test and provide feedback on?
  • where to provide feedback and get involved with development
  • brief idea of what is coming next, and when?

Next step might include review and update of:

After all the project docs are up-to-date, blogs, press articles, social network posting announcements and links should all point back at the main project site or wiki page to help build search engine optimization.

Retrieved from "https://wiki.mozilla.org/index.php?title=Labs/Release&oldid=192805"