about summary refs log tree commit diff
path: root/docs/dev
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-02-12 18:20:27 +0000
committerGitHub <noreply@github.com>2021-02-12 18:20:27 +0000
commit935830d05bcf5f0c648e636dcbc8848a201467c0 (patch)
treeff289b26eb96e2dd9fdfaf24f5c73f0f2487a2d1 /docs/dev
parent88253907f4bc3beaa7b8f2e58cb652f653f92d56 (diff)
parent8814d1368d6712fd85074d77e33be610f01566c4 (diff)
downloadrust-935830d05bcf5f0c648e636dcbc8848a201467c0.tar.gz
rust-935830d05bcf5f0c648e636dcbc8848a201467c0.zip
Merge #7655
7655: Include a commit log summary in the changelog r=matklad a=lnicola

This version omits any direct pushes, and maybe even pull requests merged from the GitHub UI. But I think it makes writing the release notes easier.

Co-authored-by: Laurențiu Nicola <lnicola@dend.ro>
Diffstat (limited to 'docs/dev')
-rw-r--r--docs/dev/README.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 9b9b18102a3..d6fae52959a 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -218,8 +218,7 @@ Release steps:
      * makes a GitHub release
      * pushes VS Code extension to the marketplace
    * create new changelog in `rust-analyzer.github.io`
-   * create `rust-analyzer.github.io/git.log` file with the log of merge commits since last release
-2. While the release is in progress, fill-in the changelog using `git.log`
+2. While the release is in progress, fill in the changelog
 3. Commit & push the changelog
 4. Tweet
 5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule.