[ruby-core:115301] [Ruby master Misc#19980] Is the Ruby 3.3 ABI frozen?

Issue #19980 has been updated by mame (Yusuke Endoh).


For now, there is no agreement/practice to freeze the ABI before its release. Therefore, it is possible that changes may be made even a day before the official release.

If we were to freeze the ABI, @naruse, the release manager, would need to make a decision to freeze the code under `include/` directory at someday before release.

When this ticket was discussed at the dev meeting, @naruse was not present, so no further discussion was done.

----------------------------------------
Misc #19980: Is the Ruby 3.3 ABI frozen?
https://bugs.ruby-lang.org/issues/19980#change-105219

* Author: mdalessio (Mike Dalessio)
* Status: Open
* Priority: Normal
----------------------------------------
I'm a co-maintainer of [rake-compiler-dock](https://github.com/rake-compiler/rake-compiler-dock) which is used to build precompiled native packages for some gems, including nokogiri, sqlite3, grpc, re2, and ruby-magic.

In the past, precompiled native gems generally released support for a new version of Ruby days or weeks after Ruby's release (for example, [Nokogiri v1.14.0 released on 2023-01-12](https://nokogiri.org/CHANGELOG.html)). In some cases, the lack of native gem support has slowed user adoption of the new version of Ruby.

This year, I'd like to see native gems release Ruby 3.3 support before the final version is released. This will encourage testing of Ruby 3.3 previews and allow users to immediately upgrade to Ruby 3.3 final when it is released.

To do that, I would like to cut a release of the rake-compiler-dock gem (and its [build containers](https://github.com/rake-compiler/rake-compiler-dock/pkgs/container/rake-compiler-dock-image)) that supports Ruby 3.3 as soon as possible (I already have a feature branch mostly working based on 3.3.0_preview1 at https://github.com/rake-compiler/rake-compiler-dock/pull/105).

Is the Ruby 3.3 ABI frozen now? If I build a native gem against Ruby 3.3.0_preview2, is there any reason to believe that it wouldn't work with Ruby 3.3 final when it is released?

Thank you for any guidance you can provide.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/