On Sat, Jun 11, 2011 at 3:39 AM, Øyvind Harboe <[email protected]> wrote: >> Please - cut a simple release now - nothing fancy, one or two RC, two weeks >> for feedback and voila. > > I want someone qualified to step up to do the work of a release manager > or I'm happy with current situation.
I can understand your point. On the other hand, I can understand what Freddie Chopin's point -- Windows users need a binary release and now many of the OpenOCD Windows users get the binaries from Freddie. And having a release version is important here. Maybe it is less important for Linux OpenOCD users since they can probably build from source by themselves. On the other hand, a release will still help -- so that distros can take it and package it. > Figure out what outstanding problems there are, work with the > list to get them sorted out, etc. There are always outstanding problems out there. So there needs to be a cut off somewhere. I think a release should be cut at either of these two points for a project like OpenOCD which is still very active and not reaching mature state. 1) Enough patches have been accumulated. 1) A certain time has been passed, say 6-months or one-year. > We can cut a 0.5 branch at some commit in the past if the master branch > has gone too far ahead by the time someone steps up. > I do not think this is normal practice... -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
