Bug #21349
closeddefault gems should have version >= 1
Description
Many of the default gems have version numbers less than 1, including venerable offerings such as net-http and yaml. Versions starting with 0 often imply a prereleased or beta status. Surely if a gem has been released as part of the base distribution of ruby itself for a number of years, it is at least worthy of a 1.0 version number. This would reduce uncertainty or confusion about the quality / production readiness of gems distributed with ruby.
From ruby 3.4.4:
benchmark (default: 0.4.0)
cgi (default: 0.4.2)
delegate (default: 0.4.0)
english (default: 0.8.0)
error_highlight (default: 0.7.0)
find (default: 0.2.0)
io-console (default: 0.8.0)
io-nonblock (default: 0.3.1)
io-wait (default: 0.3.1)
net-http (default: 0.6.0)
net-protocol (default: 0.2.2)
open-uri (default: 0.5.0)
open3 (default: 0.2.1)
optparse (default: 0.6.0)
ostruct (default: 0.6.1)
pathname (default: 0.4.0)
pp (default: 0.6.2)
prettyprint (default: 0.2.0)
pstore (default: 0.1.4)
readline (default: 0.0.4)
reline (default: 0.6.0)
resolv (default: 0.6.0)
ruby2_keywords (default: 0.0.5)
securerandom (default: 0.4.1)
shellwords (default: 0.2.2)
singleton (default: 0.3.0)
tempfile (default: 0.3.1)
time (default: 0.4.1)
timeout (default: 0.4.3)
tmpdir (default: 0.3.1)
tsort (default: 0.2.0)
un (default: 0.3.0)
weakref (default: 0.1.3)
yaml (default: 0.4.0)
Updated by hsbt (Hiroshi SHIBATA) about 1 month ago
- Status changed from Open to Rejected
Versions starting with 0 often imply a prereleased or beta status.
No, we don't use that versioning policy.