You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it proper assumption that tagged versions are released?
More interesting http://rubygems.org/pages/download lists v2.0.7 as latest release yet v2.0.8, v2.0.9, v2.1.0, v2.1.1, v2.1.2 and v2.1.3 was released.
Is there a service/place I could check what versions are released? Especially from the point of compatibility with older rubies like MRI 1.8.6 or 1.8.7.
The text was updated successfully, but these errors were encountered:
I've also been meaning to put together a document about RubyGems' branch maintenance and Ruby compatibility policies.
Important points: RubyGems 2.x will be Ruby 1.8.7 compatible. Ruby 1.8.6 compatibility was dropped around RubyGems 1.5.0. RubyGems 2.0.x will receive bug fixes as it is in Ruby 2.0.0. RubyGems 1.8.x has received bug fixes for forward-compatibility with Ruby 2.0.0, but no formal policy has been decided about further bug fixes. RubyGems 1.8.x and 2.0.x will receive security fixes.
I can find the tag v2.0.9 here: https://github.com/rubygems/rubygems/tags - but I can not find release here: http://production.cf.rubygems.org/rubygems/rubygems-2.0.9.tgz
Is it proper assumption that tagged versions are released?
More interesting http://rubygems.org/pages/download lists
v2.0.7
as latest release yetv2.0.8
,v2.0.9
,v2.1.0
,v2.1.1
,v2.1.2
andv2.1.3
was released.Is there a service/place I could check what versions are released? Especially from the point of compatibility with older rubies like MRI
1.8.6
or1.8.7
.The text was updated successfully, but these errors were encountered: