Hello, I have been working with Lucas Kanashiro in #debian-ruby to do an update from Ruby 3.4.9 to 3.4.10 in Experimental: https://salsa.debian.org/ruby-team/ruby/-/merge_requests/10
After this is done, we may want to trigger additional rebuilds here to clear up the list: https://people.debian.org/~kanashiro/debian/ruby3.4/ It looks like most marked packages have been covered: https://salsa.debian.org/ruby-team/ruby-defaults/-/wikis/Ruby-3.4-transition - I have worked through a few of these myself. Big picture, it seems logical to start preparing for the version of ruby-defaults in Experimental to be uploaded to Unstable (support both Ruby 3.3 and Ruby 3.4), then take care of Rails 8 after. It's a large transition involving coordination; even with test rebuilds, we can only get so far. The Rails 8 transition involves (at least) 164 packages, most of which could be patched for testsuite coverage and fixes for Rails 8. I can stage Rails 8 in Experimental if we generally agree that it's time for preliminary results, but I don't plan on driving the "support Ruby 3.4" transition (although I plan on helping quite a bit.) I'm expecting both transitions to take some time, but thought it would be good to ask if this order makes sense. With a careful approach, we should be able to work through both transitions, one after the other. Finally, which version(s) of Ruby are we targeting for Forky? Would it make sense to start a third transition after these two to drop 3.3, or are we expected to release Forky with 3.3 support? (I suppose 4.0 is a different question entirely.) Thanks, Simon Quigley [email protected]
