[Rubygems-developers] Stability/Maturity attribute

Michael Neumann mneumann at ntecs.de
Thu Jun 3 10:07:00 EDT 2004

On Thu, Jun 03, 2004 at 01:56:13PM +0000, Eivind Eklund wrote:
> On Thu, Jun 03, 2004 at 02:56:58PM +0200, Michael Neumann wrote:
> > Hi,
> > 
> > Wouldn't it be nice to document inside a gemspec how stable/mature the
> > software is? This way, the user does not have to search inside the
> > documentation, on the rubyforge site, or on RAA to find this
> > information.
> I think this sounds good.  However, in order for it to be really useful,
> there should probably be a general description of what is meant by
> different stability/maturity clauses.
> If nobody beat me to it, I'll try to write up a suggestion set for
> these.  I'll try to write it so it is easy to categorize your software
> into the different "levels", and so RPA can more or less just say "We'll
> enforce[1] stability level X" and have one aspect of policy in place
> (both to save on my own work, and to make the mapping between RPA and
> RubyGems clear to people that use both.)
> Sounds good to everybody?


Sourceforge/Rubyforge has those levels:

  1 - Planning
  2 - Pre-Alpha
  3 - Alpha
  4 - Beta
  5 - Production/Stable
  6 - Mature

Planning isn't very useful for gems.

Excuse my ignorance, but what's RPA?



More information about the Rubygems-developers mailing list