Skip to content

add initial versioning policy - #131

Merged
zejn merged 1 commit into
mpdavis:masterfrom
mattsb42-aws:versioning
Apr 9, 2019
Merged

add initial versioning policy#131
zejn merged 1 commit into
mpdavis:masterfrom
mattsb42-aws:versioning

Conversation

@mattsb42-aws

Copy link
Copy Markdown
Contributor

As discussed in #129, I would like to propose that python-jose officially state what versioning policy the project is following. While there seems to be tentative agreement that the project is following SemVer already, it would be great if that could be explicitly stated. This will make it much simpler for consumers of this library to reason about how to handle upgrades and will help the maintainers in deciding how changes should manifest in new versions.

@codecov

codecovBot commented Apr 8, 2019

Copy link
Copy Markdown

Codecov Report

Merging #131 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@ Coverage Diff @@## master #131 +/- ##
=======================================
Coverage 96.52% 96.52% =======================================
Files 14 14 Lines 1065 1065 =======================================
Hits 1028 1028 Misses 37 37

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5d2e03f...ae318c0. Read the comment docs.

@zejn
zejn merged commit 29e14dc into mpdavis:masterApr 9, 2019
@zejn

zejn commented Apr 9, 2019

Copy link
Copy Markdown
Collaborator

Looks good.

@mattsb42-aws
mattsb42-aws deleted the versioning branch April 9, 2019 18:31
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@mattsb42-aws@zejn