Prepare dev release for g3 roll

[elliette]

I would like to roll DevTools into g3 to fix #4524

Following instructions to prepare dev release here: https://github.com/flutter/devtools/tree/master/tool#prepare-the-release

Ran dart tool/update_version.dart auto --type dev

[elliette]

What should the CHANGELOG look like? Should I remove the TODO? Or generate the changelog (in which case we should update instructions in https://github.com/flutter/devtools/tree/master/tool#prepare-the-release)

[kenzieschmoll]

I think TODO is fine for dev release. The generate changelog tool isn't smart enough to use releases that aren't formally tagged on our repo as a 'before' data for the range of commits. Plus, the release will be going out in a couple of days so this changelog will get updated then.

[CoderDake]

perhaps we should just leave a bullet mentioning it is a dev release, so there aren't any notes needed?
Leaving todo's implies that something needs to be done and might come up later

[elliette]

Added that to #4536 :)

[kenzieschmoll]

this version should be 2.18.0-dev.0, as 2.17.0-dev.0 is actually before 2.17.0 in semantic versioning

[CoderDake]

This might need to be updated in our version bumping script.
if we wanted to make a dev version of 2.17.0 what would you expect the dev version to be?

[elliette]

Discussed offline! By default we will have the dev version be preparatory for next minor release

[kenzieschmoll]

lgtm once version is changed