On Thursday 25 June 2009, Zach Welch wrote: > Hi all, > > Here is my summary of what I think needs to be done to prepare for a > "source-only" 0.2.0 release, which will help promote OpenOCD and maybe > attract new developers that can help fix the binary distribution issue. > > ... > > So again, we need to forget about the binary distribution problems in > the OpenOCD development community for the time being. These issues will > all be resolved externally or in future releases.
I'm OK with the 0.2.0 release being "source only", with minor updates (0.2.1 etc) as needed. The download page http://developer.berlios.de/project/showfiles.php?group_id=4148 shows lots of downloads of the MS-Windows binary -- which we are not in a position to update for now! -- and most of the rest are the source tarball, not the Fedora binary. Debian unstable is using SVN, Thursday's HEAD (r2403) in fact (!)... What needs to change before 0.2.0 finalizes? Maybe a handful of patches yet. I don't see much point in stretching it out too much longer. For the record, why don't we label r2403 as "RC1"? And focus this next week on high priority fixes, aiming at an "RC2" for next Thursday's HEAD. Hoping that RC2 will be "0.2.0" ... - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
