On 18/09/14 04:42 AM, Ulrich Pegelow wrote:
...
> The balance between benefits of these changes and their downside is not
> good. Too many people rely on the current master so we cannot just leave
> it crashing until hopefully a solution is found.
>
> I strongly recomend to revert the changes that have led to the problem
> and move them into a feature branch. Only if the problem can be
> reproduced in this branch and a final fix is found it should be
> re-integrated into master.
+100.
If this was the gate that I know and love, then the
changes would be backed out for insufficient testing.
James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
https://www.jmcpdotcom.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
