-
Notifications
You must be signed in to change notification settings - Fork 34
DOCSP-48100: Consolidate minor versions #240
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -90,7 +90,7 @@ associated JIRA tickets for each release on `GitHub | |||||
|
||||||
.. _php-v2-breaking-changes: | ||||||
|
||||||
Version 2.0 Breaking Changes | ||||||
Version 2.x Breaking Changes | ||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||||||
|
||||||
This library version introduces the following breaking changes: | ||||||
|
@@ -113,15 +113,15 @@ This library version introduces the following breaking changes: | |||||
methods, you can register a :php:`CommandSubscriber | ||||||
<mongodb-driver-monitoring-commandsubscriber>` in your application. | ||||||
|
||||||
Version 1.20 Breaking Changes | ||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||||||
Version 1.x Breaking Changes | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
We don't consider bumping dependencies such as minimum PHP or server versions as "breaking changes", as that would require us to only do these in a major version. The rationale is that for PHP versions, the compatibility is checked by composer, so users on a version of PHP that is no longer supported won't be upgraded to the newer driver version and thus don't encounter a breaking change. Since the server version drops are so far behind (one year after it's marked EOL by the server team), the number of people affected is fairly low. For example, we're only now dropping support for MongoDB 4.0. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see; I moved the compatibility changes to its own section to separate it from the breaking changes |
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||||||
|
||||||
This library version introduces the following breaking changes: | ||||||
|
||||||
- Drops support for {+mdb-server+} 3.6. | ||||||
- Drops support for {+mdb-server+} 3.6 in {+php-library+} v1.20 | ||||||
|
||||||
Version 1.19 and Earlier | ||||||
~~~~~~~~~~~~~~~~~~~~~~~~ | ||||||
.. tip:: Earlier Library Versions | ||||||
|
||||||
For library versions 1.19 and earlier, see the release notes and associated | ||||||
JIRA tickets for each release on `GitHub <https://github.com/mongodb/mongo-php-library/releases>`__. | ||||||
To view breaking changes for {+php-library+} versions 1.19 and earlier, see the | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
release notes and associated JIRA tickets for each release on `GitHub | ||||||
<https://github.com/mongodb/mongo-php-library/releases>`__. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, it makes sense to call these out as breaking changes in 2.0 - people will understand that these apply to future 2.x versions as well. This helps clarify that we don't make breaking changes in minor versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed! I also added a sentence in the "Breaking Changes" introduction noting that only major version releases have breaking changes