[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian Ruby team BoF in this year's DebConf



On Wed, Apr 16, 2025 at 05:17:17PM -0300, Lucas Kanashiro wrote:
> Hi,
> 
> On Tue, 2025-04-15 at 00:31 +0200, Cédric Boutillier wrote:
> > Hi!
> > 
> > I would be happy if there was a Ruby BoF again at DebConf this year,
> > especially since I am going to attend in person this time after
> > having
> > followed remotely for many years.
> 
> Thanks for all the replies. I submitted the BoF, I'd like to already
> ask people to think/propose topics to be added to the agenda. Since I
> do not have a document ready to share yet, feel free to propose
> anything in this thread.

- A better solution for the split between gems that are shipped with
  ruby but also as standalone packages. maybe we should strip them out
  of the src:ruby upstream tarball, and not ship that code at all. e.g.:
  rubygems, bundler, rake, etc etc etc.

- should we revisit our current practice of not doing a transition for
  every new ruby version?  e.g. for trixie we skipped 3.2. if we had
  done 3.2, we would have caught several issues that we found with 3.3
  way earlier.

  This gives us more work overall, but 1) it would make the final
  transition before the release smoother because a good part of the
  issues has been fixed before the previous version and 2) the work is
  better distributed during the ~2 years of the release cycle, instead
  of concentrated on the second half of the cycle.

Attachment: signature.asc
Description: PGP signature


Reply to: