Hello,

We have a Cortex-A32 target that requires this patch for AArch32 support - 
https://review.openocd.org/c/openocd/+/5854.
Can we do something more to get the patch merged and released?

Best regards,
Plamena
________________________________
From: Antonio Borneo <borneo.anto...@gmail.com>
Sent: Friday, 23 May 2025 1:16 pm
To: OpenOCD <OpenOCD-devel@lists.sourceforge.net>
Subject: Preparing for OpenOCD v1.0.0-rc1

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe. Never provide your password!
VORSICHT: Diese E-Mail kommt von einem externen Absender. Bitte keine Links 
anklicken oder Anlagen öffnen falls Sie den Absender nicht kennen. Niemals Ihr 
Kennwort eingeben!


Hello,

we are going to tag OpenOCD v1.0.0-rc1 in around one month.
It will follow a period of code freeze, during which only patches for
bug fixes will be merged.
The release v1.0.0 is expected before the end of the year.

Why v1.0.0 ?
Because OpenOCD is 20 years old, and at such an age it's mature enough
for a cool major release.
Because today we have already merged 996 commits since last release
v0.12.0 (2023-01-14), and it's time to focus on tests and fixes.
Because it's summer and old bugs get hotter, so time to fix them.
Because, ... feel free to add your personal reason to this list! ;-)

Said that, I invite you all to report any feature still pending in
Gerrit that you absolutely want to have in v1.0.0.

Regards,
Antonio


Hilscher Development & Test Center EOOD  |  Business Park Varna - B8, 402  |  
9009 Varna | Bulgaria |  www.hilscher.com<http://www.hilscher.com>

Important Information:
This e-mail message including its attachments contains confidential and legally 
protected information solely intended for the addressee. If you are not the 
intended addressee of this message, please contact the addresser immediately 
and delete this message including its attachments. The unauthorized 
dissemination, copying and change of this e-mail are strictly forbidden. The 
addresser shall not be liable for the content of such changed e-mails.

????????:
???? ?????????? ????????? ? ??????????? ??? ???? ??????? ???????? ?????????? 
????????????? ?????????? ?? ???????? ????? ??????????. ??? ?????? ????? ?? ? ? 
??????? ?? ?????????? ???? ????????? ?? ???????? ???? ????????? ? ??????????? 
??? ???? ??????? ???? ???????????? ????????? ????????. ????????, ??????? ??? 
????????? ? ????? ???? ?? ???????????? ??????????? ? ???? ????????? ??? 
????????? ???????? ?? ?????? ? ?????? ?????????.


Reply via email to