Add release notes in the repository #1951
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
It's useful to have the release notes directly inside the repository instead of relying on Github: that lets for example users read them offline. It also lets us fill the release notes every time we add relevant features on `master` instead of having to do them all at once when we decide to make a release.
t-bast
force-pushed
the
release-notes
branch
from
a7e7f9e to
7f0f500
Compare
thomash-acinq
previously approved these changes
Sep 20, 2021
pm47
reviewed
Sep 20, 2021
Good idea, done in 75ae8dd |
pm47
approved these changes
Sep 20, 2021
Codecov Report
@@ Coverage Diff @@
## master #1951 +/- ##
==========================================
+ Coverage 87.63% 87.69% +0.05%
==========================================
Files 159 158 -1
Lines 12441 12389 -52
Branches 526 533 +7
==========================================
- Hits 10903 10864 -39
+ Misses 1538 1525 -13
|
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.
It's useful to have the release notes directly inside the repository instead of relying on Github: that lets for example users read them offline.
It also lets us fill the release notes every time we add relevant features on
masterinstead of having to do them all at once when we decide to make a release. Every time a contributor makes a PR that should be included in the release notes, we should ask the contributor to update the release notes directly inside the PR. That ensures release notes are thorough and accurate, and splits the work between all contributors.I copy-pasted the release notes of the last release (0.6.1) and create the draft release notes for the next release, so that we can start this process ASAP. I already filled the next release notes with everything noteworthy that happened since v0.6.1. @thomash-acinq can you please double-check what I put for A/B testing? And let me know if you want to add something about the changes you made to the heuristics (in particular the virtual hop cost).