Jump to: navigation, search

Release plan

109 bytes added, 10:28, 15 June 2016
no edit summary
== Detailed time schedule and checklist ==
# Just after the next release, the next default airport is decided on by a poll on the forum. The next release will be named after it.
# (On the 17th of the release month): The first Jenkins script is triggered to create <code>release/xxxx.x.0</code> branches with version xxxx.x.0.
# Jenkins creates the binaries for xxxx.x.1.
# Nightly builds are created from <code>next</code> after every push in that branch.
The process is repeated after a set number of three months (to-be-decided).
== Version files ==

Navigation menu