Hi, I'm proposing to start active preparations to officially release the next version of OpenOCD.
It would be nice to do it as quick as reasonably so that 64-bit changes can be pulled in to main branch as soon as possible (without fear of breaking existing targets right before a release). So basically I'm proposing to merge whatever is ready for merging and tag a release. Of course, it's not that simple because we need to try hard to avoid regressions (users getting OpenOCD from distribution's repositories expect any update to be no worse for their specific usecases). So if you think you know about something that works in 0.9.0 but doesn't work in current git HEAD, please do speak up! If you would like some nice and non-risky (from regressions point of view) changes to be reviewed and included in 0.10.0, please say so now. I know it's annoying many changes are not getting prompt reviews and merging, some of the changes I've sent myself are still pending review, but that's how it is currently. Usually if the change attracts attention from other users and developers, it gets in eventually, so do not hesitate to nag everybody about everything that you believe to be important. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
