From 4b1ec391a956d0a25505085cda31d5b1729a8d44 Mon Sep 17 00:00:00 2001 From: mikeller Date: Mon, 30 Mar 2020 01:10:58 +1300 Subject: [PATCH] Added announcement of the feature freeze for 4.2. --- .github/pull_request_template.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index cfcf39bd32..455ddbb25f 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,3 +1,14 @@ +## Important: Feature freeze / release candidate phase for Betaflight 4.2 + +From 25 March 2020 until the release of Betaflight 4.2.0 (scheduled for 01 May 2020), the project is in a 'feature freeze / release candidate' phase. This means: + +1. Pull requests can still be submitted as normal. Comments / discussions will probably be slower than normal due to shifted priorities; + +2. If your pull request is a fix for an existing bug, or an update for a single target that has a low risk of side effect for other targets, it will be reviewed, and if accepted merged into `master` for the 4.2 release; + +3. All other pull requests will be scheduled for 4.3, and discussed / reviewed / merged into `master` after 4.2.0 has been released. Please keep in mind that this potentially means that you will have to rebase your changes if they are broken by bugfixes made for 4.2. + + ## Important: New requirements for the submission of new and updated targets As announced earlier in https://github.com/betaflight/betaflight#betaflight-40, Betaflight 4.0 is introducing a radically new way to define targets, the so-called 'Unified Targets'.