Issue #21264 has been updated by jeremyevans0 (Jeremy Evans). If we are going to remove stdlib `Date`, I would also prefer that `Date` be a core class instead of demoted to bundled gems. A large number of Ruby libraries and applications need `Date` functionality. I wouldn't be in favor of bringing the entire `date` library into core. Specifically, I don't think we should bring in `DateTime`. There were historical reasons for `DateTime` (especially in Ruby 1.8), but few modern applications would need it. If we don't want to make `Date` a core class, since the move to bundled gems seems motivated primarily due to lack of maintainer time, I offer myself as maintainer. ---------------------------------------- Feature #21264: Extract Date library from Ruby repo in the future https://bugs.ruby-lang.org/issues/21264#change-112691 * 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.prase` 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/