Release Process and Rules

Starting with the version to be released after , the following ruleswill govern and describe how the Requests core team produces a new release.

A major release will include breaking changes. When it is versioned, it willbe versioned as vX.0.0. For example, if the previous release wasv10.2.7 the next version will be v11.0.0.

Major releases may also include miscellaneous bug fixes and upgrades tovendored packages. The core developers of Requests are committed to providinga good user experience. This means we're also committed to preservingbackwards compatibility as much as possible. Major releases will be infrequentand will need strong justifications before they are considered.

A minor release will not include breaking changes but may includemiscellaneous bug fixes and upgrades to vendored packages. If the previousversion of Requests released was v10.2.7 a minor release would beversioned as v10.3.0.

A hotfix release will only include bug fixes that were missed when the projectreleased the previous version. If the previous version of Requests releasedv10.2.7 the hotfix release would be versioned as v10.2.8.

Hotfixes will not include upgrades to vendored dependencies afterv2.6.2