File: RELEASE.md

package info (click to toggle)
ruby-fog 1.38.0-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 10,852 kB
  • ctags: 10,789
  • sloc: ruby: 69,847; xml: 1,357; makefile: 7; sh: 4
file content (40 lines) | stat: -rw-r--r-- 1,429 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# 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.md`
* 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)
* Run `rake github_release` to add release to [github release feed](https://github.com/fog/fog/releases.atom) (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)