On Wed, May 09, 2012 at 02:16:05AM +0200, Peter Stuge wrote: > > I expect more people to see the release than .git, and publishing a > release which potentially has *more* issues than the previous one > ...
I'm one of the (almost-)silent users and I expect many many more will see a release than the .git (many won't look for a .git, indeed many won't know what git is). Usually a release is far more stable, with either few or at least well-documented issues and perhaps even a commitment to fix things in the release as more are found. I can confirm some remarks that even with a release version just building OpenOCD from source can be, well let's say "trying". If asked what would I like for the next release, and I can see why I would not be so asked, I would say "easy to build, works out of the box, no fighting of config, no having to study hard to see which options to enable/disable let alone why". Sorry, but I really am just a user of this tool. Fortunately I haven't had to rely on OpenOCD and so far just tested it and more or less decided "oh well I'll just debug my target using printf". (*) I don't understand the rush to get the next release out of the door. (*) or LED patterns etc but you know what I mean John ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
