Tim Vernum 84483b26cf Fix version logic when bumping major version (#38593) ... When we are preparing to release a major version the rules around "unreleased" versions and branches get a bit more complex. This change implements the following rules: - If the tip version on the previous major is a .0 (e.g. 6.7.0) then the tip of the minor before that (e.g. 6.6.1) must be unreleased. (This is because 6.7.0 would be "staged" in preparation for release, but 6.6.1 would be open for bug fixes on the release 6.6.x line) (in VersionCollection & VersionUtils) - The "major.x" branch (if it exists) will always point to the latest minor in that series. Anything that is not the latest minor, must therefore be on a the "major.minor" branch For example, if v7.1.0 exists then the "7.x" branch must be 7.1.0, and 7.0.0 must be on the "7.0" branch (in VersionCollection)		2019-02-08 18:00:03 +11:00
..
src	Fix version logic when bumping major version (#38593)	2019-02-08 18:00:03 +11:00
build.gradle	Testing conventions now checks for tests in main (#37321)	2019-01-24 17:30:50 +02:00