8c30c8294a
release: work around GitHub Actions weirdness
2021-06-12 08:40:48 -04:00
c44d263419
release: add note about pushing changes
2021-06-12 08:13:29 -04:00
53cb9a779e
release: add step about making sure 'master' is in sync
...
Otherwise, if we start doing crate releases from the local checkout
(with git tags) and it turns out that origin/master has newer commits,
rebasing local master will then invalidate those tags.
2021-06-12 07:59:47 -04:00
21644408f2
release: tweak 'cargo outdated' advice
...
I do run --aggressive, although I've been ignoring the clap 3 update for
what seems like forever since it's still in beta.
2021-06-12 07:54:51 -04:00
beda5f70dc
doc: improve wording
...
This tightens up the wording in ripgrep's opening description. It's used
in several places, so we update all of them.
Closes #1881
2021-05-31 21:51:18 -04:00
b1e3de246c
changelog: add empty TBD section to CHANGELOG
...
And update the release checklist to mention this process.
2020-05-29 09:49:45 -04:00
0b965f900c
doc: small release checklist updates
...
In particular, explicitly note when to update the CHANGELOG.
Also, tweak the ripgrep introductory message.
2020-05-29 09:21:19 -04:00
1e9a481a66
doc: more release checklist updates
2020-05-09 11:43:37 -04:00
4b8e1f030e
doc: add more detail to release checklist
...
Getting the crate order right is important, so document it.
2020-05-09 11:12:51 -04:00
6219d29c24
doc: add 'cargo outdated' step to release checklist
...
It's just good sense to make sure everything is updated if possible.
2020-05-09 10:26:00 -04:00
fac47906e6
doc: add a release checklist
...
The steps are numerous, subtle and complex enough that it's worth
writing them down. In particular, getting the order correct is
important. (i.e., If we released to crates.io first and the GitHub
release infrastructure failed, then we'd be in a pickle.)
2020-05-08 23:24:40 -04:00
