kotovalexarian-likes-github/fog--fog
1
0
Fork 0
mirror of https://github.com/fog/fog.git synced 2022-11-09 13:51:43 -05:00
Code Releases Activity
fog--fog/RELEASE.md

41 lines
1.4 KiB
Markdown
Raw Normal View History

[docs] Creates release policy document to discuss This documents the current release policy as it appears (based on the Rakefile) but may not be comprehensive. For github issue #1406
2012-12-27 15:25:25 -05:00
# 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`)
[core] updated rake releases to generate markdown; added github_release task to publish to release feed.
2014-03-24 10:12:19 -04:00
* Run `rake changelog` to update `CHANGELOG.md`
[docs] Creates release policy document to discuss This documents the current release policy as it appears (based on the Rakefile) but may not be comprehensive. For github issue #1406
2012-12-27 15:25:25 -05:00
* Run `rake release` to prepare the release which does:
[core] Breaks down rake tasks While documenting our release process, we can see some things that don't need to be locked together are. This splits release into prepare/publish parts Now anyone can prepare a release but will not be able to publish that release without the correct access to Github and Rubygems. Adds a preflight task and adds a check for existing tags to that.
2012-12-27 16:41:28 -05:00
* 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)
[core] updated rake releases to generate markdown; added github_release task to publish to release feed.
2014-03-24 10:12:19 -04:00
* Run `rake github_release` to add release to [github release feed](https://github.com/fog/fog/releases.atom) (Requires Credentials)
[docs] Creates release policy document to discuss This documents the current release policy as it appears (based on the Rakefile) but may not be comprehensive. For github issue #1406
2012-12-27 15:25:25 -05:00
## 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)
Copy permalink