diff options
| author | worldofpeace <worldofpeace@protonmail.ch> | 2020-04-20 11:57:45 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-20 11:57:45 -0400 |
| commit | e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e (patch) | |
| tree | 903b417b9c680765537091c20616c6a928ca0e33 /.github | |
| parent | f76d7b5e418b17faac5953e4fc617fbd8d9622c1 (diff) | |
| parent | 6380be302a5da1f5200968cd358e93fa64cdc996 (diff) | |
| download | nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.tar nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.tar.gz nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.tar.bz2 nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.tar.lz nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.tar.xz nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.tar.zst nixlib-e9e9582986e638c0b0b38bf9b2bae29bcfbcac0e.zip | |
Merge pull request #85186 from worldofpeace/20.03-readme
README.md: 20.03 release
Diffstat (limited to '.github')
| -rw-r--r-- | .github/CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index a50a8a507de3..ae4f68dddc19 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -53,9 +53,9 @@ For package version upgrades and such a one-line commit message is usually suffi To [backport a change into a release branch](https://nixos.org/nixpkgs/manual/#submitting-changes-stable-release-branches): 1. Take note of the commit in which the change was introduced into `master`. -2. Check out the target _release branch_, e.g. `release-19.09`. Do not use a _channel branch_ like `nixos-19.09` or `nixpkgs-19.09`. +2. Check out the target _release branch_, e.g. `release-20.03`. Do not use a _channel branch_ like `nixos-20.03` or `nixpkgs-20.03`. 3. Use `git cherry-pick -x <original commit>`. -4. Open your backport PR. Make sure to select the release branch (e.g. `release-19.09`) as the target branch of the PR, and link to the PR in which the original change was made to `master`. +4. Open your backport PR. Make sure to select the release branch (e.g. `release-20.03`) as the target branch of the PR, and link to the PR in which the original change was made to `master`. ## Reviewing contributions |