-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jean-Christophe PLAGNIOL-VILLARD scrisse:
> I'll send a patch to sumurize all our discussion about the new release > process this WE > It will be nice to have a list of Maintainer and their role to > specify which part of OpenOCD they take care of > As everyone see the first rc1 is done the rc2 will be Monday > so please help us to stabilize the current release and do a great and > stable 0.5.0 I had liked to give this -rc1 a shot on various autobuilders to detect early build failures, but I've failed so far to see a proper signed tarball or even a git tag on the openocd repo to base upon. I've also not seen any changes to doc/manual/release.txt or a Maintainer file, even if various release details were discussed and consensus reached. Yet, an -rc2 is expected for today. I'm a bit puzzled, but maybe I'm missing some important details here. Can I expect a version bump in configure.in to reflect a release? Out of which commits are these -rcX being done? Did you perhaps forgot to push the tag? And most importantly, where are testers/packagers expected to get the tarball from? Thanks, Luca - -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S. | lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk4RhSkACgkQRqobajv7n7MsRgCbBHrCc4InVOr3VQIJ8iOn4q5J dpYAn2Tf2ZYYMXE4mJe8oolRlXIUZSwU =2JkV -----END PGP SIGNATURE----- _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
