From: khaines@...
Date: 2006-07-12T03:20:07+09:00
Subject: Re: Developmetn Releases on Rubyforge

On Wed, 12 Jul 2006 transfire@gmail.com 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 Haines