Skip to content
This repository was archived by the owner on Dec 8, 2021. It is now read-only.

Commit f7c6c16

Browse files
authored
doc: fixes for how to cut a release (#1417)
The document describing how to cut a release was still referring to `INSTALL.md`, then I realized that `ci/test-readme` really is just a place to store scripts to generate markdown, so I renamed it too.
1 parent 755c07a commit f7c6c16

File tree

6 files changed

+1
-17
lines changed

6 files changed

+1
-17
lines changed
File renamed without changes.
File renamed without changes.
File renamed without changes.

doc/cutting-a-release.md

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -26,23 +26,7 @@ git log --no-merges --format="format:* %s" \
2626
upstream/master
2727
```
2828

29-
### Update README.md
30-
31-
Update the instructions to build the library for development:
32-
33-
```bash
34-
./ci/test-readme/generate-readme.sh >README.md
35-
```
36-
37-
### Update INSTALL.md
38-
39-
Update the instructions to install the library:
40-
41-
```bash
42-
./ci/test-readme/generate-install.sh >INSTALL.md
43-
```
44-
45-
It is not recommended that you create the release branch before this PR is
29+
It is **not** recommended that you create the release branch before this PR is
4630
*merged*, but in some circumstances it might be needed, for example, if a large
4731
change that could destabilize the release is about to be merged, or if we want
4832
to create the release at an specific point in the revision history.

0 commit comments

Comments
 (0)