Engineer(s): Ross Lawley, Slav Babanin 20250-07-10: Work completed 2025-07-02: Target date set to 2025-07-07 What was accomplished since the last update? All code work finished and awaiting code reviews What's the focus over the next two weeks? Getting into main Any risks/blockers/impediments? n/a 2025-06-19: Target date set to 2025-06-26 What was accomplished since the last update? Log messages added as per SDAM spec Started adding operation name to logs What's the focus over the next two weeks? Finishing up adding operation to logs Any risks/blockers/impediments? Risk is maven central portal migration taking up time. 2025-06-09: Target date set to 2025-06-19 What was accomplished since the last update? Work paused - due to working on AWS secrets work What's the focus over the next two weeks? Working on the remaining tickets Any risks/blockers/impediments? None expected. 2025-05-22: Target date set to 2025-05-19 What was accomplished since the last update? Started phase 2 of finishing off this epic JAVA-5697 Update SDAM spec to include error messages for electionId/setVersion mismatches - in code review JAVA-5230 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor - in code review JAVA-5229 Publish TopologyDescriptionChangedEvent on topology close - in progress, core work done but may require some larger unified test infrastructure changes to report the events. What's the focus over the next two weeks? Getting the above into main Working on the remaining tickets Any risks/blockers/impediments? None expected. Engineer: Jeff Summary: Define a default set of debug logging messages that drivers should produce, and a standardized, trivial mechanism drivers should support for enabling, disabling, and configuring debug logging 2023-01-20: Setting initial target end date to 2023-02-03 Logging and command monitoring spec changes in review Supporting configurable max document length in command logging is up next