docs: add guidelines for breaking changes by aucampia · Pull Request #2402 · RDFLib/rdflib (original) (raw)
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation1 Commits5 Checks0 Files changed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
Add guidelines on how breaking changes should be approached.
The guidelines take a very pragmatic approach with known downsides, but this seems like the best compromise given the current situation.
For prior discussion on this point see:
coverage: 90.851%. remained the same when pulling f706279 on aucampia:aucampia/20230522T2045-devnote into 7860cd4 on RDFLib:main.
This was referenced
May 22, 2023
ajnelson-nist added a commit to casework/CASE-Utilities-Python that referenced this pull request
This sets case-utils and downstream Python tooling to take care in
reviewing new RDFLib releases for breaking changes. RDFLib Issue 2402
and Discussion 2395 outline an upcoming development period for RDFLib
that may see more frequent SEMVER-major version releases.
References:
Signed-off-by: Alex Nelson alexander.nelson@nist.gov
This was referenced
Jul 6, 2023