- **status**: new --> closed
- **Milestone**: 0.9.0 --> 0.10.0
- **Resolution**:  --> v0.11.0 released
- **Component**:  --> release



---

** [tickets:#277] No release since 3 years after 0.10.0 hampers collaboration 
with other projects**

**Status:** closed
**Milestone:** 0.10.0
**Created:** Wed Aug 26, 2020 12:58 PM UTC by Jelle Haandrikman
**Last Updated:** Fri Nov 06, 2020 10:06 AM UTC
**Owner:** nobody


Hello,

I tried to update the handling of OpenOCD in RIOT-OS to the current version, 
with regard of the ST-link adapter handling. However, this update can't be 
taken into account at this moment. Because the current official release is so 
old. It's not possible for RIOT (or other projects) to accomodate all versions 
on the supported platforms. 

OpenOCD hasn't issued an official release since 2017, different projects bundle 
different versions of OpenOCD nowadays. Debian has only started OpenOCD 
snapshots since May 2020. Which contains the updated ST-Link handling that 
isn't in 0.10.0. See the issue I submitted to below. 

The absence of an official release means that versions incorporated in 
distributions get out of sync. So  it remains hard to implement updates that 
take care of all the versions out in the wild. Even downloading the latest 
release of OpenOCD on the website points to version 0.10.0. Which puts people 
on the wrong footing. 

Also the whole feature set of OpenOCD has undergone significant updates since 
the latest release.  

Although a new release might incur quite some effort, it would make life a lot 
easier for downstream projects. 

The Issue for RIOT-OS I submitted. 
https://github.com/RIOT-OS/RIOT/issues/14855#issuecomment-680835175

best regards,
Jelle Haandrikman


---

Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/openocd/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/openocd/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.


Reply via email to