Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update release procedure #2141

Merged
merged 1 commit into from
Dec 15, 2023
Merged

Update release procedure #2141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions release-procedure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,17 +20,18 @@ The release announcement lives on the website, and needs to be created in the [w
First, create the initial draft of the release announcement:

``` sh
automator announcement
automator blog release
```

This will create an announcement that will initially not be published to the blog or RSS feed, but it will be available at its final URL.

Now, edit this file to finish the release announcement:

1. Add pull requests
A list of pull requests has been added to the draft automatically. Go through them, update and merge entries as appropriate, sort them into the correct categories.
1. Curate pull requests
- A list of pull requests has been added to the draft automatically.
- Update and merge entries as appropriate, sort them into the categories.
2. Write introduction
- Summarize the week's development.
- Summarize changes since last release.
- Highlight contributions.
3. Choose subtitle.

Expand Down Expand Up @@ -72,9 +73,9 @@ Create a pull request:
- Label it as `release`.
- Lock the pull request.

The pull request needs to be locked, as anything that updates it (like comments), could confuse next week's release automation (because GitHub doesn't allow sorting pull requests by merge date, unfortunately).
The pull request needs to be locked, as anything that updates it (like comments), could confuse the automation for the next release (because GitHub doesn't allow sorting pull requests by merge date, unfortunately).

Once the CI build completed successfully, merge the pull request. The release automation will now compile binaries, create a release on GitHub, and publish to [crates.io](https://crates.io/).
Once the CI build completed successfully, merge the pull request. The release automation will now create a release on GitHub, and publish to [crates.io](https://crates.io/).


## 7. Update release on GitHub
Expand Down