Add 0.7.0 AppStream release entry #1845
Closed
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
|
Nvm I just realised the quality guidelines explicitly advise against long lists of bullet points, let me rework that… |
|
Done. Perhaps not the finest piece of prose I’ve written but should do the job. |
chchwy
approved these changes
Jun 6, 2024
chchwy
force-pushed
the
appstream-release
branch
from
8b04bd8 to
0fdd17b
Compare
|
Closing as it's merged. Github doesn't seem to recognize that this PR was merged after I replaced the TODO with the actual date. |
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.
Caution
Before merging, replace the 2
TODOs in the file with the final release date and release notes URL!This is a draft for the AppStream metadata changes for the next release. I wanted to try including a changelog this time so that it can be shown in Linux app stores / software centers. The changelog is based directly on the blog post draft, with irrelevant info (such as Windows-specific entries or technical details) omitted. As the note above says, this still needs the final release date and blog post URL, so I don’t expect this to be merged until right before release.