Releasing beta version of gem (naming question)

I have a stable release of a gem mygem V1.1.x.
I have a new beta-ish version 1.2.0. I'd like to release a gem for 1.2,
however, i don't want it to become the default download until i believe
its stable.

Is there a norm for this? Do we change the name to mygem-beta or
mygem1.2.0-beta and then delete that gem when its stable ?

···

--
Posted via http://www.ruby-forum.com/.

This is called a pre-relase gem and to get one you have to name your gem
like this: mygem.1.2.0.beta, i.e. a comination of ASCII characters as
the last version number (not just "beta" is valid). To install a
prerelease gem, you have to pass the --pre option to gem:
  $ gem install mygem --pre
Otherwise RubyGems will download the current stable version.
Have a look at the coderay gem ( http://rubygems.org/gems/coderay ),
it's maintainer has published some beta gems.

Vale,
Marvin

···

Am 17.10.2010 08:44, schrieb Rahul Kumar:

I have a stable release of a gem mygem V1.1.x.
I have a new beta-ish version 1.2.0. I'd like to release a gem for 1.2,
however, i don't want it to become the default download until i believe
its stable.

Is there a norm for this? Do we change the name to mygem-beta or
mygem1.2.0-beta and then delete that gem when its stable ?

Marvin Gülker wrote in post #954889:

This is called a pre-relase gem and to get one you have to name your gem
like this: mygem.1.2.0.beta, i.e. a comination of ASCII characters as
the last version number (not just "beta" is valid). To install a
prerelease gem, you have to pass the --pre option to gem:
  $ gem install mygem --pre
Otherwise RubyGems will download the current stable version.
Have a look at the coderay gem ( http://rubygems.org/gems/coderay ),
it's maintainer has published some beta gems.

Vale,
Marvin

Thanks. Added ".pre" to the version attribute in gemspec (or if using
jeweler, then to the VERSION file), does the trick in creating a
pre-release.

···

--
Posted via http://www.ruby-forum.com/.