From: "NARUSE, Yui" Date: 2013-07-09T17:28:07+09:00 Subject: [ruby-core:55877] Re: ruby 1.9.3 p448 breaks ABI 2013/7/9 V�t Ondruch : > Dne 9.7.2013 4:03, NARUSE, Yui napsal(a): > >> Why you didn't report it before release? > > > If I had noticed it earlier, I would have reported it. I'll try to do better > next time. However, please note > > * There was only *one* day between the breakage and release of -p448. It > means there was almost no time to react. Yeah, such commits just before the release is not a good habit. It should be fixed. > It would be also helpful to know > ahead "we are going release p448 as next release, you have $TIMEPERIOD to > test". You are describing ruby security mailing list, and there's such information. > * There is ABI promised, so the ABI check should be part of release process. > If there is ABI breakage, it should be reported by upstream, not later find > by downstream If you want someone to do something in OSS, you should do. > * I'll definitely take a look on rubyci.org and I'll try to make the > abi-check failing, when the ABI is broken. I hope, that release maintainers > will pay attention. rubyci.org doesn't show vividly abi breakage yet. It exists only in the detail of debian's result. -- NARUSE, Yui