Sha256: 2cf9ac0e9fe87c3d61b382fdcbc58f2c3ae0c53a4b0d1ffcbef8d19bc7e5b0ff
Contents?: true
Size: 1.27 KB
Versions: 70
Compression:
Stored size: 1.27 KB
Contents
# Release process This is fog's current release process, documented so people know what is currently done. ## Versioning fog uses semantic versioning (http://semver.org/) ## When we release Releases occur monthly and are manually handled by fog's Benevolent Dictator Wes (@geemus). To request a new release please raise an issue. ## Prepare the release * Ensure the code is passing on the CI server [![Build Status](https://secure.travis-ci.org/fog/fog.png?branch=master)](http://travis-ci.org/fog/fog) * Ensure the code is passing for live tests (Requires Credentials for all services) * Ensure working on **master** * Update the version number (`lib/fog/version.rb`) * Run `rake changelog` to update `changelog.txt` * Run `rake release` to prepare the release which does: * Prepares the release (`rake release:prepare`) * Builds the gem * Tags the commit * Creates commits for version * Publishes the release (`rake release:publish`) * Pushes commit and tag to Github (Requires Credentials) * Pushes gem to Rubygems (Requires Credentials) ## Announce the release Once the release is prepared and uploaded it needs to be announced. * Send an email to https://groups.google.com/forum/?fromgroups#!forum/ruby-fog * Tweet as @fog on Twitter (Requires Credentials)
Version data entries
70 entries across 70 versions & 7 rubygems