lnd.xprv/docs/release-notes/release-notes-0.14.0.md

# Release Notes

# Build System

[A new pre-submit check has been
added](https://github.com/lightningnetwork/lnd/pull/5520) to ensure that all
PRs ([aside from merge
commits](https://github.com/lightningnetwork/lnd/pull/5543)) add an entry in
the release notes folder that at leasts links to PR being added.

# Code Health

## Code cleanup, refactor, typo fixes

* [Unused error check 
  removed](https://github.com/lightningnetwork/lnd/pull/5537).
* [Shorten Pull Request check list by referring to the CI checks that are 
  in place](https://github.com/lightningnetwork/lnd/pull/5545).
* [Added minor fixes to contribution guidelines](https://github.com/lightningnetwork/lnd/pull/5503).

## Database

* [Ensure single writer for legacy
  code](https://github.com/lightningnetwork/lnd/pull/5547) when using etcd
  backend.

# Contributors (Alphabetical Order)
* ErikEk
* Zero-1729
docs/release-notes: add new in-tree location for release notes In this commit, we add a new folder within the `docs` directory that will house the release notes for all versions of `lnd` going forward. Moving to use `git` for the release notes rather than the normal drafting procedure lets us keep track of the set of changes more consistency over time, lets contributors add their release notes over time, and also means we'll no longer need to do a crunch at the tail end of the release process to fill in the set of release notes. For the 0.13.1 release notes, I've done a scan and added anything that has been merged since the last major version tag. In a follow up change, we'll add a new Github action that fails the build if an entry in the release notes linking to the newly added PR isn't committed as well. Until then, any PRs merged in should ensure that they add an entry within the relevant milestone. 2021-06-22 05:21:42 +03:00			`# Release Notes`

docs/release-notes: add entry for new release notes pre-submit check 2021-07-16 05:22:12 +03:00			`# Build System`

			`[A new pre-submit check has been`
			`added](https://github.com/lightningnetwork/lnd/pull/5520) to ensure that all`
docs/release-notes: add section re merge commit exemption 2021-07-20 01:31:48 +03:00			`PRs ([aside from merge`
			`commits](https://github.com/lightningnetwork/lnd/pull/5543)) add an entry in`
			`the release notes folder that at leasts links to PR being added.`
docs/release-notes: add entry for new release notes pre-submit check 2021-07-16 05:22:12 +03:00
invoice: unused error check 2021-07-17 16:00:05 +03:00			`# Code Health`

			`## Code cleanup, refactor, typo fixes`
mod+GitHub: shorten PR template, bump golang to 1.15 The golang version always needs to be in sync between the go.mod, the PR checklist and the installation instructions. We also shorten the Pull Request template by removing everything that we have a CI check for and just refer to those checks instead. 2021-07-20 10:32:53 +03:00
invoice: unused error check 2021-07-17 16:00:05 +03:00			`* [Unused error check`
mod+GitHub: shorten PR template, bump golang to 1.15 The golang version always needs to be in sync between the go.mod, the PR checklist and the installation instructions. We also shorten the Pull Request template by removing everything that we have a CI check for and just refer to those checks instead. 2021-07-20 10:32:53 +03:00			`removed](https://github.com/lightningnetwork/lnd/pull/5537).`
			`* [Shorten Pull Request check list by referring to the CI checks that are`
docs: minor fixes to contribution guidelines 2021-07-20 16:57:43 +03:00			`in place](https://github.com/lightningnetwork/lnd/pull/5545).`
			`* [Added minor fixes to contribution guidelines](https://github.com/lightningnetwork/lnd/pull/5503).`
invoice: unused error check 2021-07-17 16:00:05 +03:00
docs: update release notes 2021-07-20 16:16:04 +03:00			`## Database`

			`* [Ensure single writer for legacy`
			`code](https://github.com/lightningnetwork/lnd/pull/5547) when using etcd`
			`backend.`

docs/release-notes: add new in-tree location for release notes In this commit, we add a new folder within the `docs` directory that will house the release notes for all versions of `lnd` going forward. Moving to use `git` for the release notes rather than the normal drafting procedure lets us keep track of the set of changes more consistency over time, lets contributors add their release notes over time, and also means we'll no longer need to do a crunch at the tail end of the release process to fill in the set of release notes. For the 0.13.1 release notes, I've done a scan and added anything that has been merged since the last major version tag. In a follow up change, we'll add a new Github action that fails the build if an entry in the release notes linking to the newly added PR isn't committed as well. Until then, any PRs merged in should ensure that they add an entry within the relevant milestone. 2021-06-22 05:21:42 +03:00			`# Contributors (Alphabetical Order)`
docs: minor fixes to contribution guidelines 2021-07-20 16:57:43 +03:00			`* ErikEk`
			`* Zero-1729`