On Nov 25, 2008, at 1:19 PM, Steve Franks wrote:
we are not guessing, we are creating a release branch that will be as suchfrozen except for major bug fixes. if after testing (month or so) all is good then we tag a release 1.0.Might I also suggest that 1.0 be available to download as a .tgz or simliar file? Most of the automated package systems I know of (i.e. FreeBSD ports) like to deal with release .tgz files. They get a little leery about building things for a OS distribution from SVN, and I'd really like to get OpenOCD into the standard set of FreeBSD packages. Yes, it can be automated from SVN, but I've had several higher-up developers inquire with raised eyebrows as to wether it's the best policy. Since I've only recently left win32, I'll assume they know what they are talking about... Best, Steve _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
It is common practice for an open-source project to release a version as a tar of the source code. I expect we will release a source code tar, linux binaries, and win32 binaries.
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
