Add release changelogs for v0.28.0 #13
Merged
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
gmourier
requested changes
Jun 8, 2022
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
dichotommy
suggested changes
Jun 8, 2022
There was a problem hiding this comment.
It's my first time editing a release changelog in a while, so I wasn't sure if I should edit things like the header levels.
On the docs we try never to use multiple H1s in the same article, or to skip a header number (i.e. don't jump from H1 to H3). But this may be an aspect of your template, so feel free to ignore those particular suggestions.
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
gmourier
requested changes
Jun 9, 2022
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
dichotommy
reviewed
Jun 13, 2022
Co-authored-by: Tommy <68053732+dichotommy@users.noreply.github.com>
|
Waiting for the last naming changes if needed on meilisearch/specifications#157 before giving a final review. Other than that, everything looks great to me! |
|
@gmourier I let this PR open until the official v0.28.0 is out. I've updated the PR description to make my expectations clearer |
curquiza
commented
Jun 14, 2022
17 tasks
gmourier
requested changes
Jun 24, 2022
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
curquiza
force-pushed
the
release-v0.28.0
branch
from
60a7e66 to
4ac38d9
Compare
gmourier
reviewed
Jun 27, 2022
Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
gmourier
requested changes
Jul 7, 2022
Comment on lines
+7
to
+8
| <!-- The following line should NOT be put in the official release changelogs --> | ||
| ⚠️ Since this is a release candidate (RC), the official documentation is not updated yet, but will be ready for the official v0.28.0 release. The work-in-progress documentation is available [here](). |
There was a problem hiding this comment.
Suggested change
| <!-- The following line should NOT be put in the official release changelogs --> | |
| ⚠️ Since this is a release candidate (RC), the official documentation is not updated yet, but will be ready for the official v0.28.0 release. The work-in-progress documentation is available [here](). |
There was a problem hiding this comment.
So you can remove it directly from github before the release 🤓
There was a problem hiding this comment.
I will not remove it from this PR, so that I can copy/paste in my next release changelog
However I will not put it in the v0.28.0 changelog on Monday haha
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.
Here are the huge changelogs for the v0.28.0 release