[Cherrypy-users] Re: Thoughts about the CherryPy project

[Justus P. <ju...@ry...>]

On 2006-01-02, Michael Goettsche <goo...@mi...> wrote:
> The release number 2.1 indicates stability.

A release number doesn't indicate anything in and of itself. It
indicates whatever that particular project wants it to mean. Some
projects follow the old linux kernel model, some follow the gcc/emacs
model, some come up with their own cute/weird way (smalleiffel uses
negative numbers slowly approaching 0; blosxom uses imaginary numbers to
denote unstable releases).

When gcc goes from 3.3 to 3.4 it signifies a major change; cherrypy
could very well be the same way. Or it could mean "it has been six
months since we last had a stable release". Or anything else unless the
cherrypy devs have a public release strategy and naming convention.

Given that cherrypy2 is practically a completely different project than
cherrypy1 I always thought a gcc naming convention made more sense...that
2.1 -> 2.2 meant a major change and 2.1.0 -> 2.1.1 meant a minor change.
Then someday in the distant future when cherrypy undergoes massive
changes such that it can automatically solve world hunger while playing
Quake it'll become cherrypy 3.0 :)

Justus