On Nov 23, 2008, at 9:27 AM, Øyvind Harboe wrote:
On Sat, Nov 22, 2008 at 12:54 PM, Spen <[EMAIL PROTECTED]> wrote:Hi, I think its about time openocd made a release 1.0.I propose we create a openocd_rel_1_0 branch that will be frozen (except formajor bugs) after a month we make a release. Any objections/comments?Instead of trying to *guess* when is a good time to cut a branch, lets just pick a version everybody is happy with and work from that. Development continues in SVN trunk as usual. I think a 6 month release cycle makes sense. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Speaking from the experience of coordinating releases for large and small software projects, there is never a version that everyone is happy with. You need to pick a point where all the new features that you want in are in, make a branch, and then fix the branch until it is stable enough for release. Since this is a 1.0, any set of features is sufficient. If we make a 1.0 branch, we can work on fixing bugs in that branch while new features (the new jtag tap syntax for example) are developed in trunk.
-- 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
