On Sat, Jun 11, 2011 at 9:31 AM, Freddie Chopin <[email protected]> wrote: > On 2011-06-10 21:57, Tomek CEDRO wrote: >> >> Freddie, why dont you become a release engineer? The work is now done >> for 0.4.0 I guess its only a matter of snapping the source tree and >> making a build as you do everyday :-) > > I really don't know the ways of "release manager" (; Oyvind says you should > be "qualified" and I don't consider myself to be that.
If you start by creating a list of open issues that we should fix and then posting that list to the mailing list and incorporating feedback, then you're half a release engineer already. Here the trick is to try to represent the interests of the community rather than your own. Also we have to make a decision of what we're not going to fix for the release. At some point a certain commit in the git master branch would be the point of a release and you declare so on the list, we tag it and were done. Once we have the tag, there are scripts in git that you'd have to look into that creates source release packages. I am not keen on OpenOCD project providing and support binaries, I want to pass that buck to "package managers". -- Ø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
