Version numbering for release DECISION!

[Joerg Sonnenberger]

On Mon, Mar 28, 2005 at 10:21:21AM -0800, Matthew Dillon wrote:
>     I do not like using PRODUCTION or STABLE, at least not in a release
>     branch that has gone through only normal release engineering.  I would
>     prefer we just call releases and sub-releases RELEASE and not
>     differentiate between the original release and commits made to the
>     release branch (other then bumping the sub-version).

Let's just call the branch RELEASE_x_y and have some form of tagging
for the release branch point. That should be enough for source users.

For image names, something like is patch level would be perfect.
E.g. DragonFly-1.2.iso as name of the release image and DragonFly-1.2p1.iso
after the first patch has been applied. That allows a user to keep track
of what she has.

Joerg