Wish there a way to mark a Rubyforge release as “official” so that a
later development releases wouldn’t become the default package/gem.
What solutions to this do others use?
T.
On Wed, 12 Jul 2006 [email protected] wrote:
Wish there a way to mark a Rubyforge release as “official” so that a
later development releases wouldn’t become the default package/gem.What solutions to this do others use?
Bad ones? i.e. not doing “development” releases often because I don’t
want them to be seen as non-development releases.
I think Daniel’s suggestion – to not release a gem to RubyForge if it
is
a development release – is a good one. Other than that, I think it
comes
down to versioning and release naming as the only current options.
Kirk H.
[email protected] wrote:
I think Daniel’s suggestion – to not release a gem to RubyForge if it is
a development release – is a good one. Other than that, I think it comes
down to versioning and release naming as the only current options.
On second though, testing the gem is important too and I imagine some
of my users still want the convenicen of the gem even for development
versions…
One thing I thought of was prefixing dev versions with 0. so version
1.5.0’s dev version would be 0.1.5.0.
Btw in gems versioing does it support dashes and do they sort before
dots? Eg.
1.5.0, 1.5.0-2, 1.5.0-1, 1.4.9
Thanks,
T.