On Tue, Feb 11, 2025 at 02:38:33PM +0530, Pirate Praveen wrote: > > On 2/11/25 9:29 AM, Lucas Kanashiro wrote: > > Hi, > > > > On 10/02/2025 16:35, Pirate Praveen wrote: > > > Hi team, > > > > > > Now that ruby 3.3 migrated to testing and rack 3 close to migration, > > > we can look at rails 7 transition. > > > > > > I have started a pad here, > > > > > > https://pad.debian.net/p/rails7 > > > > > > At the top, we have the list of regressions found by britney > > > experimental pseudo excuses. We need to look at each and move them > > > to correct sections like packages that can be removed (from testing > > > or from the archive itself - leaf packages that are dead upstream) > > > or packages we care / need to fix. If you are working on a package > > > fix, add your name to avoid duplication. > > > > > > You need to login with salsa to edit the pad. > > > > Thanks for creating this pad, Praveen. I'd like to ask to not start the > > rails 7 transition in unstable before we remove support for ruby3.1 [1]. > > The timeline that I think is ideal is: > > > > 1) Migrate ruby-rack 3 to testing > We are very close to finishing it. > > 2) Remove ruby3.1 support > > So far only two packages showed regressions in > https://release.debian.org/britney/pseudo-excuses-experimental.html#ruby-defaults > > jruby and libguestfs > > > 3) Start rails 7 transition > > > We have a lot of work to do for rails 7 before we upload to unstable, we can > definitely wait till 1 and 2 is finished. > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095713
We can and should start that work, let's just not do it with rails 7 in unstable before the existing transitions are done with. I'm looking into the rails 7 `newapp` autopkgtest and I think I made it work.
signature.asc
Description: PGP signature
