[#115244] [Ruby master Feature#19987] add sample method to Range — "horv77@... (Andras Horvath) via ruby-core" <ruby-core@...>
Issue #19987 has been reported by [email protected] (Andras Horvath).
6 messages
2023/11/05
[#115247] [Ruby master Feature#19988] AI for inner code behavior analysis at runtime — "horv77@... (Andras Horvath) via ruby-core" <ruby-core@...>
Issue #19988 has been reported by [email protected] (Andras Horvath).
3 messages
2023/11/05
[#115404] Ruby 3.2.2 - rbconfig.rb's MAKEFILE_CONFIG — Jay Mav via ruby-core <ruby-core@...>
Hello Ruby Dev Team,
4 messages
2023/11/17
[ruby-core:115488] [Ruby master Misc#19980] Is the Ruby 3.3 ABI frozen?
From:
"mdalessio (Mike Dalessio) via ruby-core" <ruby-core@...>
Date:
2023-11-27 14:12:33 UTC
List:
ruby-core #115488
Issue #19980 has been updated by mdalessio (Mike Dalessio). I've shipped a pre-release of rake-compiler dock, [v1.4.0.rc1](https://gith= ub.com/rake-compiler/rake-compiler-dock/releases/tag/1.4.0.rc1), which supp= orts compilation of native gems using Ruby 3.3.0-preview3. This is only useful for testing purposes right now, see: - [ext: ruby 3.3 support by flavorjones =B7 Pull Request #3038 =B7 sparklem= otion/nokogiri](https://github.com/sparklemotion/nokogiri/pull/3038) - [ext: add experimental support for ruby 3.3 by flavorjones =B7 Pull Reque= st #429 =B7 sparklemotion/sqlite3-ruby](https://github.com/sparklemotion/sq= lite3-ruby/pull/429) If the Ruby core team and the release manager choose to freeze the ABI, the= n I would immediately release this as v1.4.0 and gem maintainers could star= t cutting releases with Ruby 3.3 support. ---------------------------------------- Misc #19980: Is the Ruby 3.3 ABI frozen? https://bugs.ruby-lang.org/issues/19980#change-105418 * Author: mdalessio (Mike Dalessio) * Status: Open * Priority: Normal ---------------------------------------- I'm a co-maintainer of [rake-compiler-dock](https://github.com/rake-compile= r/rake-compiler-dock) which is used to build precompiled native packages fo= r some gems, including nokogiri, sqlite3, grpc, re2, and ruby-magic. In the past, precompiled native gems generally released support for a new v= ersion of Ruby days or weeks after Ruby's release (for example, [Nokogiri v= 1.14.0 released on 2023-01-12](https://nokogiri.org/CHANGELOG.html)). In so= me cases, the lack of native gem support has slowed user adoption of the ne= w 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 releas= ed. To do that, I would like to cut a release of the rake-compiler-dock gem (an= d its [build containers](https://github.com/rake-compiler/rake-compiler-doc= k/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. --=20 https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- [email protected] To unsubscribe send an email to [email protected] ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-c= ore.ml.ruby-lang.org/