Skip to content

Does this project follow semantic versioning? #33

Description

@alvassin

What is the best way to specify this project in requirements? Can i use this project with ~= operator and specify it like retry~=0.9.2?

From one hand, this library has early version, but from another, i see that some files are 3 years old, so it looks pretty mature. So, does this project follow semver, where version consists of the MAJOR.MINOR.PATCH segments (described below)?

  • MAJOR for incompatible API changes,
  • MINOR for new functionality in a backwards compatible manner
  • PATCH version when you make backwards compatible bug fixes

If it is, don't you mind to add this information to README/CHANGELOG (so, others could find answer for this question quickly)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions