diff options
| author | Bundlerbot <bot@bundler.io> | 2019-08-27 22:46:39 +0000 |
|---|---|---|
| committer | Bundlerbot <bot@bundler.io> | 2019-08-27 22:46:39 +0000 |
| commit | c8081842e4e0a4f553831a5d688fb537f9481dd0 (patch) | |
| tree | 889e4e88b609af7fcf98aa9bf6841ba95e239d68 | |
| parent | 3db1ace2f59e3db5a7e1d641b646874bcee80c9d (diff) | |
| parent | 99df87b7b05fc6b88eead741b6141828c912db7e (diff) | |
| download | bundler-c8081842e4e0a4f553831a5d688fb537f9481dd0.tar.gz | |
Merge #7332
7332: Fix version number in release playbook r=deivid-rodriguez a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was that I'm about to release bundler, but I'm unsure which one is the right version number.
### What was your diagnosis of the problem?
My diagnosis was that the release playbook is probably wrong, because looking at https://rubygems.org/gems/bundler/versions, we don't really ship `.pre.0`. versions.
### What is your fix for the problem, implemented in this PR?
My fix is to document `.pre.1` as the first prerelease on a minor series, since that's what we usually do.
Co-authored-by: David RodrÃguez <deivid.rodriguez@riseup.net>
| -rw-r--r-- | doc/playbooks/RELEASING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/playbooks/RELEASING.md b/doc/playbooks/RELEASING.md index 9cfdeda58b..475a748dcc 100644 --- a/doc/playbooks/RELEASING.md +++ b/doc/playbooks/RELEASING.md @@ -112,7 +112,7 @@ _anything_ wrong as the release manager. #### Branching Minor releases of the next version start with a new release branch from the -current state of master: `1-12-stable`, and are immediately followed by a `.pre.0` release. +current state of master: `1-12-stable`, and are immediately followed by a `.pre.1` release. Once that `-stable` branch has been cut from `master`, changes for that minor release series (1.12) will only be made _intentionally_, via patch releases. |