Situation

IMHO, we should create a new release with all the new additions. 🎉 😄

Proposal

We should finish/clarify the following issues before we create the release:

• Deprecate module level functions #229: "Deprecate module level functions"
• Shift focus on semver.VersionInfo.* functions #235: "Shift focus on semver.VersionInfo.* functions"
• Deprecate missing module-level functions (like semver.compare, semver.match, ...) #236: "Deprecate semver.match?"
• First implementation of next_version #222 : "First implementation of next_version"
• Add __getitem__ method to allow easy access to version parts #138: "Add __getitem__ method"

Questions

Should we create a new 2.9.2 release or 2.10.0? The latter seems to be more appropriate according to the semver specification item 7 (emphasize by me):

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

@python-semver/reviewers @gsakkis: Opinions?

Update 2020-04-25: Add pr #222 to the list.