As part of improving the quality of Autoware code and processes, we are setting dates for steps in the development of Autoware. Here are the proposed dates.
- 1 April, 2019 Feature selection freeze. All features to be developed must be added to the 1.12 milestone by this date.
- 20 May, 2019 Feature development freeze. If a PR providing a feature is not merged by this date, then the feature will slip to 1.13. This includes documentation. After this date, only PRs that fix bugs or add tests will be accepted.
- 24 June, 2019 Code freeze. If a feature still has critical bugs at this date, it will be reverted and it will slip to 1.13. If it has minor bugs, it will be labeled as “experimental”.
- 1 July, 2019 Release 1.12.
The reason for the long lead time between feature development freeze and code freeze is because we need to have sufficient time to test things properly. We can’t run through all new features on a vehicle with sufficient confidence in a week or two, especially if we need time to fix bugs found.
It is likely that this pattern will be changed for the 1.13 release based on what we learn this time around about things like the long lead times and managing bugs.
Please comment and propose alternative dates if you feel these are not good.