On Wednesday, January 02, 2013 03:20:27 Jonathan M Davis wrote: > On Wednesday, January 02, 2013 10:19:54 bearophile wrote: > > Jonathan M Davis: > > > Why? > > > > Because the two numbers "2.060" and "2.061" look very very > > similar, so people that see them risk thinking they are just two > > nearly identical releases of the same compiler. But many months > > have passed between those two versions, many bugs have being > > removed, several features have being introduced, and so on (just > > look at the difference in the zip size between the two versions), > > so it's better for the users to be aware that some probably some > > user code will need to be fixed or improved to run on the 2.061. > > And how is that any different from any other release?
Two to three months generally of the past few years, so this release has been much delayed in comparison, but that doesn't really change anything. You have the same risk of things breaking that you normally do. Any bug fix risks breaking code. The only difference is that there are more bugs which have been fixed. It's quite possible that way more code broke between 2.059 and 2.060 than it did between 2.060 and 2.061. I see no reason to call out this release as being particularly dangerous. If anyone is concerned about the amount of time between releases, they can see that easily enough in the changelog. - Jonathan M Davis
