On Sun, Apr 26, 2015 at 09:28:05AM +0200, Freddie Chopin wrote: > On 26.04.2015 09:07, Paul Fertser wrote: > > It would be really nice to shorten the release cycle. Would it be > > acceptable for everybody if we release more often (e.g. twice a year) > > Such schedule was actually planned some time ago, but - as we know - the > deadline was missed (;
If the majority agrees that the decision seems wrong in the hindsight, we can try to do it better next time. But there's a tradeoff here: is it really ok for the OpenOCD's public image to have a release with buggy features, even if they're marked EXPERIMENTAL? Where and how to mark them so people won't get an impression that "OpenOCD is buggy" and "every new release something breaks, I better not update"? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
