Dates for 1.12 development and release

Autoware
1

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.

1 Like
2

Is there any chance that some contributors, including me, are not allowed to set the milestone in the issue?
Seems like I cannot set the milestone to the issue.

3

Ok, I thought that GitHub allowed setting the milestone when you created an issue.

So as to not open up the flood gates to issues on the milestone, we’ll keep it that way. Post the issue you want to add here and a maintainer can add it for you if there is no debate about it.

4

@gbiggs @Kosuke_MURAKAMI I’d also suggest making a explicit mention to at least 1 of the maintainers in the issue so that it doesn’t get missed

1 Like
5


Okay, want to add these features.

6

I would like to add these features.

7

@gbiggs Please state always the timezone for any deadlines you set, Autoware development is not just in Japan, but some standard must be agreed. What are ROS practices regarding deadlines?

8

Except where otherwise stated, it’s all UTC.

9

Unfortunately, due to accumulated delays from getting PRs merged and then conducting in-car testing, we have found several small issues in 1.12.0-alpha.2. We cannot put out a beta when there are bugs we know need to be fixed, and it will take a week or so to get the fixes done and merged. This means that we need to delay the release of 1.12 for a week. The new dates are:

  • 1 July, 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”.
  • 8 July, 2019 Release 1.12.

We will be reviewing the 1.12 development cycle after the 1.12 release, and one of the things we will consider is how to prevent the same delay happening next time.

1 Like