Hi Peter,
I've discovered that it takes a *LONG* time before teams learn that you
*CAN* have the master branch be releasable at all times if you don't accept
unfinished work or work that doesn't move the product forward.
We *do* have the tools and methods to keep track of unfinished work in
progress(Gerrit in our case), but this didn't used to be the case and old
habits die hard.
I don't know what regressions that we've picked up in 0.7.0, but we should
strive not to submit code that makes OpenOCD worse and then submit 0.7.1 as
soon as we have the regressions compared to 0.6.0 fixed.
In the case of a regression submitted from Gerrit, that does not have to be
a problem if we revert it *soon* and then simply resubmit a new change with
the original unfinished work.
Can we revert the changes that went into 0.7.0 and resubmit them to Gerrit?
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434
http://www.zylin.com/
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
