Bump the version.

[Yury-Fridlyand]

Signed-off-by: Yury-Fridlyand [email protected]

Description

Bump release version to 1.1.0.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dblock]

We should be doing this every time after a release, preparing for the next developer iteration.

[Yury-Fridlyand]

This goes to the main, not to 1.1.0 branch.

[harshavamsi]

We should be doing this every time after a release, preparing for the next developer iteration.

@dblock correct me if I'm wrong here, but shouldn't this be done before a release. The release artifacts still point to the older 1.0.0 version unless we update them here first.

I understand what you mean now, lost in interpretation...

[dblock]

@harshavamsi My favorite reason why version should be incremented to the next development iteration right after a release is because I don't ever want to rebuild code with changes that happened after the said release. So let's say we release 1.0.0, the next patch version is always 1.0.1 per semver (incremented immediately) and there's never again a 1.0.0 build. If someone PRs a new feature, they increment the version to 1.1.0 in their PR, again per semver, otherwise we're always ready to release a (security) patch 1.0.1.