DOCSP-33315 v4.4 (#4856)

* 4.4.25 Release Notes Finalize

* *

* *

* *

* snooty bump

Author: ianf-mongodb

snooty.toml

@@ -201,7 +201,7 @@ latest-lts-version = "4.4"
 last-supported-version = "4.2"
 version-last = "4.2"
 version-dev = "4.3"
-release = "4.4.24"
+release = "4.4.25"
 pgp-version = "{+version+}"
 package-name-org = "mongodb-org"
 package-name-enterprise = "mongodb-enterprise"

source/includes/changelogs/releases/4.4.25.rst

@@ -3,37 +3,77 @@
 4.4.25 Changelog
 ----------------
 
-Sharding
-~~~~~~~~
-
-- :issue:`SERVER-70973` Balancer should stop iterating collections when 
-  there are no more available shards
-- :issue:`SERVER-71627` Refreshed cached collection route info will 
-  severely block all client request when a cluster with 1 million chunks
-- :issue:`SERVER-80491` Expose more granular metrics around balancing 
-  round
-- :issue:`SERVER-80703` Avoid traversing routing table in 
-  MigrationDestinationManager
+Operations
+~~~~~~~~~~
 
+- :issue:`SERVER-58534` Collect FCV in FTDC
+- :issue:`SERVER-77610` Log session id associated with the backup cursor
 
 Internals
 ~~~~~~~~~
 
-- :issue:`SERVER-58534` Collect FCV in FTDC
-- :issue:`SERVER-73394` Remove misleading operationsBlockedByRefresh 
+- :issue:`SERVER-52452` Enable feature flag for Make taking self-managed
+  backups in 4.4+ as safe as possible
+- :issue:`SERVER-68132` Remove Feature Flag for PM-2076
+- :issue:`SERVER-70973` Balancer should stop iterating collections when
+  there are no more available shards
+- :issue:`SERVER-71627` Refreshed cached collection route info will
+  severely block all client request when a cluster with 1 million chunks
+- :issue:`SERVER-73394` Remove misleading operationsBlockedByRefresh
   metrics
-- :issue:`SERVER-77610` Log session id associated with the backup cursor
+- :issue:`SERVER-75255` Remove all outdated entries from
+  backports_required_for_multiversion_tests.yml
 - :issue:`SERVER-78149` Implement the mongos fsync (lock : true) command
 - :issue:`SERVER-78150` Implement the mongos fsyncUnlock command
+- :issue:`SERVER-78151` Add fsyncLock status to the mongos currentOp
+  command
+- :issue:`SERVER-78153` Unlock the config server primary via the mongos
+  fsyncUnlock command
+- :issue:`SERVER-78156` Test the mongos fsync with lock command with
+  distributed transactions
+- :issue:`SERVER-78793` Add a timeout to the mongos FSync Lock Command
+- :issue:`SERVER-78813` Commit point propagation fails indefinitely with
+  exhaust cursors with null lastCommitted optime
+- :issue:`SERVER-78987` Remove the free monitoring code from
+  mongodb/mongo repo
+- :issue:`SERVER-79025` Mongos Fsync with lock command should use mongos
+  fsyncUnlock command
 - :issue:`SERVER-79127` Error when $vectorSearch limit is <= 0
-- :issue:`SERVER-80694` FCV gate null lastKnownCommittedOpTime behavior 
-  in oplog getMore
+- :issue:`SERVER-79252` Add the system-perf bootstrap file to the task
+  Files section
+- :issue:`SERVER-79885` Oplog fetching getMore should not set null
+  lastKnownCommittedOpTime if it is not using exhaust cursors
+- :issue:`SERVER-80140` Use the $currentOp to verify that
+  fsyncLockWorker threads are waiting for the lock
+- :issue:`SERVER-80488` Avoid traversing routing table in balancer split
+  chunk policy
+- :issue:`SERVER-80491` Expose more granular metrics around balancing
+  round
+- :issue:`SERVER-80499` Fix use-after-free in planShardedSearch
+- :issue:`SERVER-80544` Fix incorrect wait in
+  runSearchCommandWithRetries
+- :issue:`SERVER-80678` Remove an outdated test case
+- :issue:`SERVER-80694` [v4.4] FCV gate null lastKnownCommittedOpTime
+  behavior in oplog getMore
+- :issue:`SERVER-80703` Avoid traversing routing table in
+  MigrationDestinationManager
+- :issue:`WT-8157` Fix format-abort-recovery-stress-test timeout
+  condition
 - :issue:`WT-8570` Do not increase oldest ID during recovery
-- :issue:`WT-8702` Limit oldest id to recovered checkpoint snapshot in 
+- :issue:`WT-8614` Make format.sh more verbose for failure diagnosis
+- :issue:`WT-8702` Limit oldest id to recovered checkpoint snapshot in
   recovery
-- :issue:`WT-8709` RTS: Do not hold the oldest id of logged tables
-- :issue:`WT-10449` Do not save update chain when there are no updates 
+- :issue:`WT-8709` RTS: Do not hold the oldest id of logged tables.
+- :issue:`WT-8825` Fix test_checkpoint_snapshot05 expected value
+  validation failure
+- :issue:`WT-9248` Fix test_checkpoint_snapshot05 failure and convert
+  python tests to use stats logic wait
+- :issue:`WT-10449` Do not save update chain when there are no updates
   to be written to the history store
-- :issue:`WT-10522` Fix a bug that leads to an unexpected aborted 
+- :issue:`WT-10522` Fix a bug that leads to an unexpected aborted
   tombstone on update chain
-- :issue:`WT-11374` Fix comparison of txnid to timestamp in row_modify
+- :issue:`WT-11374` Fix comparison of txnid to timestamp in row_modify
+  (v5.0)
+- :issue:`WT-11492` Assertion fires in test_checkpoint_snapshot05 on
+  windows-64
+

source/release-notes/4.4.txt

@@ -44,23 +44,23 @@ Patch Releases
 
 .. _4.4.25-release-notes:
 
-4.4.25 - Sept 29, 2023
-~~~~~~~~~~~~~~~~~~~~~~
+4.4.25 - Sep 29, 2023
+~~~~~~~~~~~~~~~~~~~~~
 
 Issues fixed:
 
-- :issue:`SERVER-78813` Commit point propagation fails indefinitely 
-  with exhaust cursors with null lastCommitted optime
-- :issue:`SERVER-79885` Oplog fetching getMore should not set null 
-  lastKnownCommittedOpTime if it is not using exhaust cursors
-- :issue:`SERVER-80140` Use the $currentOp to verify that 
-  fsyncLockWorker threads are waiting for the lock
-- :issue:`SERVER-80488` Avoid traversing routing table in balancer 
-  split chunk policy
-- :issue:`SERVER-80499` Fix use-after-free in planShardedSearch
-- :issue:`SERVER-80544` Fix incorrect wait in 
-  runSearchCommandWithRetries
+- :issue:`SERVER-76299` Report writeConflicts in serverStatus on
+  secondaries
+- :issue:`SERVER-78828` LDAP host timing data can be inconsistent during
+  sorting
+- :issue:`WT-11031` Fix RTS to skip tables with no time window
+  information in the checkpoint 
 
+- :issue:`SERVER-70973` Balancer should stop iterating collections when there are no more available shards
+- :issue:`SERVER-71627` Refreshed cached collection route info will severely block all client request when a cluster with 1 million chunks
+- :issue:`SERVER-78813` Commit point propagation fails indefinitely with exhaust cursors with null lastCommitted optime
+- :issue:`WT-8570` Do not increase oldest ID during recovery
+- :issue:`WT-10449` Do not save update chain when there are no updates to be written to the history store
 
 - `All JIRA issues closed in 4.4.25
   <https://jira.mongodb.org/issues/?jql=project%20in%20(SERVER%2C%20TOOLS%2C%20WT)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.4.25>`_