Breaking changes between v3.5.2 and v3.6.0

[rite2hhh]

Bug summary

The contributing docs state the following:

Within a major version changes must be backwards compatible

The most recent release v3.6.0 renamed some methods without bumping the major version:

• createmeta_fieldtypes renamed to project_issue_fields
• createmeta_issuetypes renamed to project_issue_types

Projects using jira-python were pinned to jira~=3.0 to protect from backwards incompatible changes.
This release however did not bump the MAJOR version after removing methods.

Is there an existing issue for this?

• I have searched the existing issues

Jira Instance type

Jira Server or Data Center (Self-hosted)

Jira instance version

9.4.5

jira-python version

3.6.0

Python Interpreter version

3.8

Which operating systems have you used?

• Linux
• macOS
• Windows

Reproduction steps

# 1. Given a Jira client instance
jira: JIRA
# 2. When I call the function createmeta_issuetypes() with necessary args
jira.createmeta_issuetypes(*args)
# 3. I see an error

AttributeError: object has no attribute 'createmeta_issuetypes'

Stack trace

N/A

Expected behaviour

Within the same MAJOR version, I expect the library to be backwards compatible.

Additional Context

No response