Skip to content

Commit ce80cf2

Browse files
authored
Merge pull request #342 from github/release-2.11.1
Bump version: 2.11.1
2 parents bd82bbf + 84c3521 commit ce80cf2

File tree

5 files changed

+475
-13
lines changed

5 files changed

+475
-13
lines changed

.ruby-version

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
2.4.0

RELEASING.md

Lines changed: 26 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,28 @@
11
# Making a backup-utils release
22

3-
1. Install the debian devscripts package:
4-
`sudo apt-get install devscripts`
5-
2. Add a new version and release notes to the `debian/changelog` file:
6-
`dch --newversion 2.6.0 --release-heuristic log`
7-
You can use `make pending-prs` to craft the release notes.
8-
3. Rev the `share/github-backup-utils/version` file.
9-
4. Tag the release: `git tag v2.0.2`
10-
5. Build that tarball package: `make dist`
11-
6. Build the deb package: `make deb`. All the tests should pass.
12-
7. Draft a new release at https://github.com/github/backup-utils/releases, including the release notes and attaching the tarball and deb packages.
13-
The dist tarball you should upload has the git revision in the file name, i.e. something like `github-backup-utils-v2.5.0.tar.gz`
14-
8. Push the head of the release to the 'stable' branch.
3+
## Automatic Process from chatops (internal to GitHub only)
4+
5+
1. `.ghe backup-utils-release 2.12.0`
6+
7+
## Automatic Process from CLI
8+
9+
1. Install the Debian `devscripts` package:
10+
`sudo apt-get install devscripts`
11+
2. Run `GH_AUTHOR="Bob Smith <[email protected]>" GH_RELEASE_TOKEN=your-amazing-secure-token script/release 2.12.0`
12+
13+
## Manual Process
14+
15+
In the event you can't perform the automatic process, or a problem is encountered with the automatic process, these are the manual steps you need to perform for a release.
16+
17+
1. Install the Debian `devscripts` package:
18+
`sudo apt-get install devscripts`
19+
2. Add a new version and release notes to the `debian/changelog` file:
20+
`dch --newversion 2.12.0 --release-heuristic log`
21+
You can use `make pending-prs` to craft the release notes.
22+
3. Rev the `share/github-backup-utils/version` file.
23+
4. Tag the release: `git tag v2.12.0`
24+
5. Build that tarball package: `make dist`
25+
6. Build the deb package: `make deb`. All the tests should pass.
26+
7. Draft a new release at https://github.com/github/backup-utils/releases, including the release notes and attaching the tarball and deb packages.
27+
The dist tarball you should upload has the revision in the file name, i.e. something like `github-backup-utils-v2.12.0.tar.gz`
28+
8. Push the head of the release to the 'stable' branch.

debian/changelog

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,13 @@
1+
github-backup-utils (2.11.1) UNRELEASED; urgency=medium
2+
3+
* Refresh the existing indices when restoring Elasticsearch indices to cluster #328
4+
* Fix failure to restore 2.9/2.10 backups to 2.11 prevented by incorrect detection of the audit log migration #333
5+
* Use git to generate short name for SSH multiplex control path #335
6+
* Remove use of --literally when computing arbitrary shasum #338
7+
* Remove -o option from ps use #341
8+
9+
-- Colin Seymour <[email protected]> Thu, 05 Oct 2017 14:47:56 +0000
10+
111
github-backup-utils (2.11.0) UNRELEASED; urgency=medium
212

313
* Use calculated routes when backing up storage data from a cluster #318

0 commit comments

Comments
 (0)