Incremented version to 4.1.0.
This commit is contained in:
mikeller
parent
9ad2cc8445
commit
2fd00ea935
|
|
@ -17,17 +17,6 @@ All subsequent rules exclude F3 based targets:
|
|||
3. For changes to existing targets, the change needs to be applied to both the 'legacy' format target definition in `src/main/target/` and a new Unified Target config in `unified_targets/configs/`. If no Unified Target configuration for the target exists, a new Unified Target configuration will have to be created and submitted alongside the proposed change.
|
||||
|
||||
|
||||
## Important: Feature freeze / release candidate phase for Betaflight 4.0
|
||||
|
||||
From 01 Mar 2019 until the release of Betaflight 4.0.0 (scheduled for 01 Apr 2019), 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.0 release;
|
||||
|
||||
3. All other pull requests will be scheduled for 4.1, and discussed / reviewed / merged into `master` after 4.0.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.0.
|
||||
|
||||
|
||||
## Important considerations when opening a pull request:
|
||||
|
||||
1. Pull requests will only be accepted if they are opened against the `master` branch. Pull requests opened against other branches without prior consent from the maintainers will be closed;
|
||||
|
|
|
|||
23
README.md
23
README.md
|
|
@ -41,33 +41,10 @@ For this reason, and because the effort required to remove features from STM32F3
|
|||
This does not mean that it won't be possible to use these flight controllers after this point in time - they will still work fine when used with the last release of 4.0, just as there are thousands of users who are still enjoying their STM32F1 based flight controllers with Betaflight 3.2.5. We will also strive to keep these versions supported in new releases of configurator, so that users still using these flight controllers will be able to configure them with the same configurator that they use to configure their STM32F4 and STM32F7 based boards.
|
||||
|
||||
|
||||
### Betaflight 4.0
|
||||
|
||||
As you might have learned from the [Betaflight GitHub page](https://github.com/betaflight/betaflight), our next release will be 4.0. Betaflight 4.0 will be the culmination of years of work that started in 2016 with the introduction of remappable resources, and it will drastically change the way how Betaflight is built and distributed. To you as the user, not much in how you download and install the Betaflight firmware will change, but you will get some noticeable improvements:
|
||||
|
||||
- we’ll have to spend less time on maintaining and releasing the firmware, meaning that we’ll have more time to work on new and exciting features;
|
||||
- manufacturers will have an easy way to release custom configurations for all of their boards and ready-to-fly (including RX setup and tuning) craft based on original Betaflight firmware - you will no longer be stuck on using old firmware, or recreating your configuration from scratch;
|
||||
- the tinkerers amongst you will be able to share Betaflight firmware with your home built improvements amongst your friends without having to build and distribute separate targets for everybody’s board.
|
||||
|
||||
*(These changes are planned for F4 and F7, F3’s flash space limitations mean we won’t be able to fit all of this in.)*
|
||||
|
||||
We are almost there with the implementation of these changes, but since they are quite complex, and getting ‘almost there’ doesn’t buy us much, we have decided that we need to take more time to complete them, make sure the way users can use the firmware still works as expected, and properly test the new firmware. For this reason we have decided to **postpone the planned release date for Betaflight to 01 April 2019**. We will keep doing monthly releases of Betaflight 3.5 with bugfixes and new / updated targets in the meantime.
|
||||
|
||||
|
||||
To get the latest update from us, you can now also visit our webpage at <https://betaflight.com/>.
|
||||
|
||||
In addition to the drastic changes mentioned above, Betaflight 4.0 will have a number of other exciting new features and improvements:
|
||||
|
||||
- yet again improved flight performance;
|
||||
- 'Launch control' mode;
|
||||
- switchable profiles for the OSD layout.
|
||||
|
||||
## Events
|
||||
|
||||
| Date | Event |
|
||||
| - | - |
|
||||
| 01 March 2019 | Start of feature freeze / Release Candidate window for Betaflight 4.0 |
|
||||
| 01 April 2019 | Planned [release](https://github.com/betaflight/betaflight/milestone/20) date for Betaflight 4.0 |
|
||||
| 01 September 2019 | Planned [release](https://github.com/betaflight/betaflight/milestone/30) date for Betaflight 4.1 |
|
||||
|
||||
## Features
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
|
||||
#define FC_FIRMWARE_NAME "Betaflight"
|
||||
#define FC_VERSION_MAJOR 4 // increment when a major release is made (big new feature, etc)
|
||||
#define FC_VERSION_MINOR 0 // increment when a minor release is made (small new feature, change etc)
|
||||
#define FC_VERSION_MINOR 1 // increment when a minor release is made (small new feature, change etc)
|
||||
#define FC_VERSION_PATCH_LEVEL 0 // increment when a bug is fixed
|
||||
|
||||
#define FC_VERSION_STRING STR(FC_VERSION_MAJOR) "." STR(FC_VERSION_MINOR) "." STR(FC_VERSION_PATCH_LEVEL)
|
||||
|
|
|
|||
Loading…
Reference in New Issue