[Rubygems-developers] Trunk version of rubygems should always be > released version

Phil Hagelberg technomancy at gmail.com
Mon Jun 15 12:16:02 EDT 2009

Chad Woolley <thewoolleyman at gmail.com> writes:

> I bumped the trunk version of RubyGems to  I previously
> discussed [1] why this makes sense.
> To summarize, this makes it much easier for people writing and testing
> with CI against the RubyGems API, especially if they have embedded
> version checks to support backward- and forward-compatibility with
> older or unreleased versions of RubyGems.
> The version should be changed to something appropriate before the next
> release. is arbitrary and interim, I don't care what it is,
> as long as it is > 1.3.4.  As soon as the 1.3.4 gem was released,
> trunk was NOT version 1.3.4 anymore.

We've got all the logic for prerelease versions in the Gem::Version
class. We could use it for RubyGems' version itself rather than just
versions of gems, since is not actually accurate either without
moving to an "odd for development, even for release" scheme.


More information about the Rubygems-developers mailing list