7 Sep
2015
7 Sep
'15
12:05 p.m.
On 09/07/2015 04:57 PM, Simon Peyton Jones wrote:
Merging and releasing a fix to the stable branch always carries a cost: it might break something else. There is a real cost to merging, which is why we've followed the lazy strategy that Ben describes.
A valid point, but the upside is that it's a very fast operation to revert if a release is "bad"... and get that updated release into the wild. Regards,