Re: 1.8.x, YAML, and release management

Acceptable or not matz releases 1.8.4 this Saturday.  It's hard to 
believe he reschedules.  And the 1.8 branch has already been frozen for 
1.8.4 release.  It's too late.

As I wrote in [ruby-core:6938], there cannot be any 1.10.x releases.  
This means the version number we can use are very limited. So I strongly 
disagree with wasting our precious 1.8.5 to release in a second after 1.8.4.

In short, it sounds like a pie in the sky to me.

Ryan Davis wrote:

> I'm concerned that 1.8.3's acceptance of non-backwards-compatible  
> changes to YAML is setting a bad precedence for ruby release  
> management. I don't think that point (read: bug-fix) releases should  
> accept and release anything that would break compatibility with  
> versions of the same major.minor value. Further, I don't think that  
> backwards incompatibility should be introduced on minor revs without  
> a minor rev in-between marking such a feature as deprecated.
>
> If this is the general consensus, I'd like to see the format change  
> in YAML be rolled back for 1.8.4 or for a soon-to-follow 1.8.5 to put  
> 1.8 back on track. If it is not the general consensus, I'd like to  
> put this on the table for discussion.