-
Notifications
You must be signed in to change notification settings - Fork 1.1k
BUMP 3.12.0b0 #586
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
BUMP 3.12.0b0 #586
Conversation
client side field level encryption (`PYTHON-2472`_). | ||
- Fixed a bug that prevented PyMongo from retrying writes after | ||
a ``writeConcernError`` on MongoDB 4.4+ (`PYTHON-2452`_). | ||
- Fixed a memory leak caused by failing SDAM monitor checks on Python 3 (`PYTHON-2433`_). |
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.
Almost all of these were fixed in 3.11.3 (or earlier 3.11 releases). Can we remove them?
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.
Can you also copy the 3.11.2 and 3.11.3 Changelog entries to this file?
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.
OK. I was a bit confused about how we want this to be reflected... Since the git histories diverged and are not common between 3.11.x and 3.12.x I thought duplicating everything in 3.12.x was the way to go... Doesn't adding the 3.11.x sections here seem to imply that 3.12.0b0 builds on the source tree of 3.11.3?
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.
The changelog shouldn't need to match the git branch history all the time. If users want a full breakdown of all the tickets they can look at the jira issues or git commits but I don't think we need to duplicate changelog entries for bugs fixed log ago. It would be different if 3.12.0 was released and we needed to fix the same bug in 3.11.4 and 3.11.1. In that case the bug fix would go under both 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.
Ok sounds good.
No description provided.