versioning scheme and breaking changes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reviewing the project's current versioning and release process, then examine the breaking change described for version 3.17. Done means the project follows semantic versioning for incompatible, compatible, and bug-fix changes, with a clear migration path for restoring the previous behavior.
Written by the indexing model from the issue text.
Description
Hi,
Would be great if you could change the current versioning scheme to respect the most used semantic versionning:
Summary
Given a version number MAJOR.MINOR.PATCH, increment the:MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.
It's a pain every time we update our dependencies, we have to remember that assertj has breaking changes even though only minor version were updated.
By the way, we're stuck on version 3.17 because of this change:
Breaking change: disable bare name getter by default, to get the previous behaviour back, call Assertions.setExtractBareNamePropertyMethods(true);
What's the simplest way to get the previous behaviour? Adding this line in every test?
Regards
- Dominant language
- Java
- Stars
- 130
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from assertj/assertj-db
-
assertj/assertj-db#324 · 1 comment · 1 assignee ·
-
question
Difficulty 3/5 1-2 days Newbie friendliness 32/100
assertj/assertj-db#292 · 1 comment ·
-
question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
assertj/assertj-db#290 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
assertj/assertj-db#259 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
assertj/assertj-db#206 ·
All issues in assertj/assertj-db
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·