Some questions/comments: - if we look at the current way we work with OpenOCD, we just commit stuff to the master branch without regards to a release. I would like this to continue in the same manner, which I don't think is in conflict with what you write.
- You create a fork of OpenOCD at the openocd mirror and create a release branch based upon some stable point in the past(or tip of master branch if that's the case). Push to a fork of OpenOCD. Release goes ahead according to your plan. You can rewrite your release branch on your mirror. - Once the release is ready, I(or another maintainer) push the release branch to the official repository. The branch is then final is never rewritten. > Merge window close this sunday 17th june sp? July 17. is OK by me. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
