mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-03-02 18:35:00 +01:00
Code Issues Projects Releases Wiki Activity

releases: update with niftynei's notes from release 0.7.3

Browse source
This commit is contained in:
lisa neigut 2019-10-28 18:31:45 -05:00 • committed by Christian Decker
parent 82a2c6b02d
commit c581fd9956
1 changed files with 18 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
doc/MAKING-RELEASES.md
View file

@ -6,18 +6,25 @@ Here's a checklist for the release process.
1. Talk to team about whether there are any changes which MUST go in 1. Talk to team about whether there are any changes which MUST go in
this release which may cause delay. this release which may cause delay.
2. Create a milestone for the *next* release, and go though issues and PR 2. Look through outstanding issues, to identify any problems that might
and mark accordingly. be necessary to fixup before the release. Good candidates are reports
3. Ask the most significant contributor who has not already named a of the project not building on different architectures or crashes.
release to name the release (use devtools/credit). CC previous namers 3. Identify a good lead for each outstanding issue, and ask them about
and team. a fix timeline.
4. Create a milestone for the *next* release on Github, and go though
open issues and PRs and mark accordingly.
5. Ask (via email) the most significant contributor who has not
already named a release to name the release (use devtools/credit to
find this contributor). CC previous namers and team.
### Prepering for -rc1 ### Preparing for -rc1
1. Check that CHANGELOG.md is well formatted, ordered in areas, 1. Check that CHANGELOG.md is well formatted, ordered in areas,
covers all signficant changes, and sub-ordered approximately by user impact covers all signficant changes, and sub-ordered approximately by user impact
& coolness. & coolness.
2. Update the CHANGELOG.md with [Unreleased] changed to -rc1. 2. Update the CHANGELOG.md with [Unreleased] changed to v<VERSION>-rc1. Note that
you should exactly copy the date and name format from a previous
release, as the `build-release.sh` script relies on this.
3. Create a PR with the above. 3. Create a PR with the above.
### Releasing -rc1 ### Releasing -rc1
@ -41,8 +48,8 @@ Here's a checklist for the release process.
### Tagging the Release ### Tagging the Release
1. Update the CHANGELOG.md; remove -rcN in both places, and add an 1. Update the CHANGELOG.md; remove -rcN in both places, update the date, and
[Unreleased] footnote URL from this new version to HEAD. add an [Unreleased] footnote URL from this new version to HEAD.
2. Add a PR with that release. 2. Add a PR with that release.
3. Merge the PR, then `git pull && git tag -s v<VERSION> && git push --tags`. 3. Merge the PR, then `git pull && git tag -s v<VERSION> && git push --tags`.
4. Run `tools/build-release.sh` to build the non-reprodicible images 4. Run `tools/build-release.sh` to build the non-reprodicible images
@ -69,5 +76,6 @@ Here's a checklist for the release process.
### Post-release ### Post-release
1. Add a new '[Unreleased]' section the CHANGELOG.md with empty headers. 1. Add a new '[Unreleased]' section to the CHANGELOG.md with empty headers.
2. Look through PRs which were delayed for release and merge them. 2. Look through PRs which were delayed for release and merge them.
3. Update this file with any missing or changed instructions.