Hi all, If there is still room for small fixes before 1.0.0, I would like to at least partially address the register force-read bug described in [1]. Full and proper resolution will mean revisiting of the register and caching API, as Antonio pointed out in his review comment. That is obviously not feasible for 1.0.0.
Instead, as an interim solution for 1.0.0, I propose a hotfix [2] that will at least ban the problematic operation (which would otherwise silently destroy cached but not-yet-written register values). Would you please have a moment to review [2]? Thank you, Jan [1] https://review.openocd.org/c/openocd/+/8070 [2] https://review.openocd.org/c/openocd/+/9737 ________________________________ From: Antonio Borneo <[email protected]> Sent: Friday, May 8, 2026 8:41 PM To: OpenOCD <[email protected]> Subject: OpenOCD: last call for v1.0.0-rc1 Hi all, we have already merged 1509 commits in the 40 months that have passed since OpenOCD v0.12.0 (Jan 14, 2023)! That's an average of 1.25 commits per day! While the content for v1.0.0 is already big enough, we still have a few minor patches that should be merged soon. Then, I would like to proceed to tag v1.0.0-rc1, after which only fixes would be merged till the final tag. Please ping asap if you have any commit pending in gerrit that should absolutely go in the release. Also, please check that nothing is missing in the NEWS file in https://review.openocd.org/c/openocd/+/7689 For the future, I would like to propose reducing the time between two releases, starting from after next v1.0.0. What about fixing the merge window to N month? I think we could reasonably choose N between 6 and 12 month, then stick to it. Feedbacks are welcome. Regards, Antonio
