Issue #21264 has been updated by Eregon (Benoit Daloze). Do we have examples of the maintenance overhead to just keep date as a default gem? I would think because it's stable and hasn't changed in a long time that it would need little maintenance. It also seems not prone to many security concerns. From a quick look at https://github.com/ruby/date/pulls?q=is%3Apr+is%3Aclosed it seems mostly automated dependencies updates and few other changes. I recall it used to be pure Ruby but was rewritten as a C extension, maybe that causes more maintenance overhead? ---------------------------------------- Feature #21264: Extract Date library from Ruby repo in the future https://bugs.ruby-lang.org/issues/21264#change-112795 * Author: hsbt (Hiroshi SHIBATA) * Status: Open ---------------------------------------- Note: This is not for Ruby 3.5. `Date` and `DateTime` has no primary maintainer in 10+ years. I would like to deprecate `date` via bundled gems for reducing our maintenance time especially @nobu. But `Time.parse` and `Time.strptime` are widely used now. How do we deprecate `date` library? 1. Migrate `Date._strptime`, `Date.strptime` and `Date._parse` to `Time`. The current `Date` is migrated as bundled gems. 2. Migrate `Date` to the bundled gems. `Time.parse` and `Time.strptime` warns if `date` is not found. 3. Keep the current situation 4. ... Does anyone have another idea? -- https://bugs.ruby-lang.org/