On Wednesday 10 February 2010, Edgar Grimberg wrote: > Hi, > > Looking over the trac list, it looks that there are only some minor > cosmetics tickets to be fixed for this release.
I see tickets #4 (regression in helptext framework), #16 (stm32 unlock information shortage), and #17 (seems like a bad imx31 board config) ... of which #4 and #16 are somewhat cosmetic, but #4 is still a regression. How about that one arm11 issue where "load_image" sometimes flaked out on i.MX32? https://lists.berlios.de/pipermail/openocd-development/2010-January/014444.html Or was that the thing that went away when you used the right config? > I believe that we can safely cut a new RC, give it a new round of > tests and prepare for 0.4 final. > Volunteers for bagging and tagging? That's one of my tasks for now. My open question is about that i.MX31 load_image thing -- potential regression. Is it really there? I've been waiting for the regressions to get resolved before cutting another RC ... Spen fixed one (yay!), I got that ARM11 GDB thing, and you chased some STR7 issues; but that's about it. Regressions are supposed to be release blockers, regardless of other bug status. Ideally, an RC2 would be *VERY* short. This release cycle hasn't gone as quickly as I wanted, mostly because of unresolved regressions. - Dave > Regards, > Edgar > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
