libobjc: Remove Traditional Objective-C runtime API

Nicola Pero nicola.pero@meta-innovation.com
Wed Jun 8 17:38:00 GMT 2011


> No.  The next number is for the next release, and ideally, we want to sit on it for another 10 years or so.  We offer no compatibility before the RM says, done with the release.  Up until then, you can twiddle, after that, no more changes to the abi, though, you can bug fix it.

Sounds good.  That was my original understanding - one ABI version per release.  For GCC 4.6.0 we bumped
the version number after the end of phase 1, which made sense to me, so I was expecting we'd do the same
for GCC 4.7.0.

But, as Jakub seemed to urge me to bump the version number right now, I got confused about whether there was
an expectation of more than one bump per release; maybe to distinguish snapshots from one another or
something like that ?

Anyhow, we have done the bumping well in advance of the 4.7.0 release and we all seem to agree on what
we should be doing (one bump per release), so it's all good. ;-)

Thanks



More information about the Gcc-patches mailing list