1
0
Fork 0
mirror of https://github.com/betaflight/betaflight.git synced 2025-07-15 04:15:44 +03:00

Merge pull request #9654 from mikeller/add_4_2_release_freeze_announcement

Added announcement of the feature freeze for 4.2.
This commit is contained in:
Michael Keller 2020-04-05 00:41:08 +13:00 committed by GitHub
commit cb8ab75475
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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 ## 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'. 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'.