On Wed, May 18, 2022 at 11:00:58AM +0200, Antonio Borneo wrote: > Dear OpenOCD developers, > > it's probably time to think about a new release of OpenOCD. > v0.11.0 was tagged in March 2021, more than one year ago. > There are already 686 commits merged after v0.11.0 covering several > improvements and fixes and dealing with jimtcl syntax changes.
Excellent timing. I'd been meaning to ask about the next release, or if a v0.11.1 would be appropriate (the libusb upgrade issue has show up in Debian unstable). > My proposal is to wait until the end of the summer vacations and, > during the first weeks of September 2022, tag v0.12.0-rc1 and enter in > code freeze. Then testing and code fixes would be the main activities > till the v0.12.0 release, hopefully before the end of 2022. > > This email is sent to: > - get feedback if there is any reason to further delay this proposed schedule, > - invite you all to propose in advance the code you want to get merged > before the code freeze. Debian is looking at starting to freeze for the next stable release in January 2023, so a release by the end of 2022 would work perfectly from my point of view. I'll make sure the rcs get uploaded to unstable for some testing prior to that. J. -- ... I have found the monster - the monster is us.
