CHANGELOGs: uniform and fix some inconsistencies #274
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version got yanked because the `gpu_socket` feature introduced in this release was causing problems (see [rust-vmm#265](rust-vmm#265)). Starting with the next version (v0.16.1), the `gpu_socket` feature was removed. Signed-off-by: Stefano Garzarella <[email protected]>
This version got yanked because the `gpu_socket` feature introduced in this release was causing problems (see [rust-vmm#265](rust-vmm#265)). Starting with the next version (v0.16.1), the `gpu_socket` feature was removed. Signed-off-by: Stefano Garzarella <[email protected]>
Every time I do a release I notice this difference between changelogs in this workspace, so let's try to uniform them by using the form used in vhost-user-backend: without square brackets in the title of the release and the `v` as prefix (v0.0.0). Also fixed some difference in how we link PRs, let's follow the most used way: [[#000]](url) Signed-off-by: Stefano Garzarella <[email protected]>
stefano-garzarella
requested review from
Ablu,
eryugey,
germag,
jiangliu,
sboeuf and
slp
as code owners
|
I based this on top of #273 so we don't need to fix the conflicts. Marking as draft till we have it merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the PR
Every time I do a release I notice this difference between
changelogs in this workspace, so let's try to uniform them by using
the form used in vhost-user-backend: without square brackets in the
title of the release and the
vas prefix (v0.0.0).Also fixed some difference in how we link PRs, let's follow the
most used way: [#000]
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.