Release plan for 2020 / LTS: Difference between revisions

m
→‎PR: https://sourceforge.net/p/flightgear/mailman/message/36975121/
m (→‎Compositor: https://sourceforge.net/p/flightgear/mailman/message/36974362/)
m (→‎PR: https://sourceforge.net/p/flightgear/mailman/message/36975121/)
Line 39: Line 39:


Contents: https://sourceforge.net/p/flightgear/mailman/message/36974362/
Contents: https://sourceforge.net/p/flightgear/mailman/message/36974362/
== Publicity ==
the ‘publicity’ around this would be:
* you can use 2018.x ‘forever’ if it works for you
* once 2020.1 is created, people should test aircraft using it and report bugs, since it will represent the feature-set for 2020.2, aka the new stable release
(this is also already true of 2019.1.)
After the 2020.2 branches exist, everyone should focus on that in terms of testing and quality, and since next will likely be a bit of a mess. (It might even make sense to make nightly builds to build from 2020.2 branch, until 2020.2 is released)<ref>https://sourceforge.net/p/flightgear/mailman/message/36975121/</ref>


== References ==
== References ==
{{Appendix}}
{{Appendix}}