Hi all, We have reached the scheduled release window. Are we ready to jump through it, or do obstacles remain in our path? I would like to release the 0.2.0 archives on the project files section of the berliOS site, so packagers may begin to integrate these into their distributions.
As of this writing, I am unaware of any blocking or critical bugs in the OpenOCD source code, and most outstanding fixes and cleanup can be scheduled to appear in later releases. I plan to commit the README and INSTALL file changes that I posted recently, as well as other "improve the distribution package" class fixes that are spotted during the final review and distribution process.* So, this is "last call" for patches to be considered for the 0.2.0 release: post 'em or postpone 'em. Unless there is an unexpected flood of activity, I believe that I could push out a 0.2.0 source release in the next 24-48 hours. Otherwise, does the community know of any reason to hold this countdown? Cheers, Zach Welch Corvallis, OR * I have attached a patch that will also be applied as part of my earlier series (i.e. patch 3 of 2). Any other touch-ups like this?
Extend 'make dist' to produce both .tar.bz2 and .zip archives, to complement to the standard .tar.gz package. Now, pick your poison! --- configure.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ====== only in patch2: unchanged: --- configure.in (revision 2429) +++ configure.in (working copy) @@ -3,7 +3,7 @@ [OpenOCD Mailing List <[email protected]>]) AC_CONFIG_SRCDIR([src/openocd.c]) -AM_INIT_AUTOMAKE([-Wall -Wno-portability]) +AM_INIT_AUTOMAKE([-Wall -Wno-portability dist-bzip2 dist-zip]) AM_MAINTAINER_MODE AM_CONFIG_HEADER(config.h)
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
