Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2026-03-16 09:16:32 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Releasing Tracks (textile)

Jyri-Petteri Paloposki 2020-07-17 13:18:40 +03:00
parent 2b05063e68
commit 52a3e90d8b
1 changed files with 5 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

11
Releasing-Tracks.textile

@ -3,19 +3,17 @@ These steps are for maintainers with commit access.
# _(Major release only)_ Make sure documentation is up to date in master. Don't change the version number yet!
** /README.md
** everything in /doc
# _(Major release only)_ Create maintenance branch for release. For example:
<pre><code>git checkout -b 2.0_branch</code></pre>
# _(Major release only)_ Update badges in README to point to the new branch (e.g. Travis)
# _(Major release only)_ Pin all gem versions using pessimistic version constraints matching the current Gemfile.lock
# Update version numbers and check copyright dates
** /README.md
** everything in /doc
** /config/initializers/tracks.rb (comment out the git date)
** /config/initializers/tracks.rb
# _(Major release only)_ Push new branch to upstream:
<pre><code>git push upstream 2.0_branch</code></pre>
<pre><code>git push upstream 2.0</code></pre>
# Tag the release:
<pre><code>git tag v2.0
<pre><code>git tag -a v2.0
git push upstream --tags</code></pre>
# Create release in GitHub, adding a description of the changes.
# _(Major release only)_ Update the version numbers in master to the next development milestone
** /README.md
** everything in /doc
@ -23,5 +21,6 @@ git push upstream --tags</code></pre>
# Publicize the new release
** Post on the Tracks website
** Update the IRC topic
** Update the Gitter topic
** Email the mailing list
** Post to Twitter