Release Process

The intention of this page is to document the release process, so that anyone taking over responsibility for this task has a reference for all steps involved.

The release manager needs the following in order to complete this process:


 * Access to the Google Code downloads page
 * Access to the OpenMW facebook page
 * Access to the OpenMW Twitter account
 * An account on the OpenMW Wordpress
 * Access to the OpenMW Youtube Account

The current Podcaster traditionally produces a video commentary to accompany each release.

Release process steps
The OpenMW team is proud to announce the release of version 0.27.0! Grab it from our Downloads Page for all operating systems. This release brings the first official release of OpenCS, the OpenMW team’s efforts to bring an open source solution for editing content for OpenMW. OpenCS is in an early Alpha state, please take that into consideration when testing! See the full notes below.
 * 1) The project lead calls for release packages to be built and tested
 * 2) Once the release packages have been tested sufficiently, the project lead will call for release, and tag the release on GitHub
 * 3) At this point, the Podcaster begins working on a release video
 * 4) * Guidelines for doing this may be found here
 * 5) The Release Manager then writes the release announcement, using the changelog in the readme
 * 6) The release announcement has the following components:
 * 7) An intro paragraph, which summarizes the release and directs readers to the downloads page. Example:
 * 1) A link to the release video, crediting the Podcaster
 * 2) A list of critical Known Issues from the release
 * 3) * Any un-fixed known critical issues from the last release are carried over
 * 4) * Any new known issues found during development and release testing are added
 * 5) A list of changes, taken from the release readme, and rewritten to be understandable by normal users
 * 6) * Reference the bug reports on the bug tracker https://bugs.openmw.org/ to understand and rewrite the changelog items
 * 7) The release announcement is then posted on the forum for approval/edits by the team
 * 8) Once the video is done, release packages are built, and release announcement is approved, the Release Manager does the release
 * 9) All release packages are uploaded to the Google Code
 * 10) The Linux binary packages
 * 11) The Windows executable packages
 * 12) The OS X package
 * 13) The release source, which is taken from https://github.com/zinnschlag/openmw/releases and re-packaged to not have a top-level folder, and renamed to match the naming convention of previous source releases
 * 14) The Release Announcement is posted to the Wordpress blog
 * 15) * If the youtube video has not been made public yet, make it public on the OpenMW youtube account
 * 16) * TODO: raevol needs to figure out why he can't embed the youtube video...
 * 17) A tweet is made on the OpenMW Twitter announcing the release and linking to the website
 * 18) A post is made on the OpenMW facebook announcing the release
 * 19) * Do a Picture post, using a screenshot from the release, so that people can re-share the post
 * 20) * You can cheat and just screenshot the release video if getting a good screenshot of the release isn't working
 * 21) * Paste the plaintext version of the release announcement as the description of the picture
 * 22) Post on the OpenMW forum announcing that the release has been completed