Article development led by
I’m working on a small, open-source
project in my free time and trying to
figure out a reasonable way to number
releases. There are about 10 of us working on the project right now, and there
seem to be 10 different opinions about
when we should roll out the major and
minor numbers for our project. Since
the software is only in the alpha stage,
I thought it was premature to come up
with a numbering scheme; but once
someone else posted it on our mailing
list we decided we should tackle the
problem now so we don’t have to think
about it again later. When you’re working on software, when do you roll out a
new version number?
averse to aversion
You have 10 developers and you have
a good version-
can be used to
track the change in
a piece of software.
only 10 opinions? I was expecting you
to say you had 20 opinions, so right
from the start it looks like you’re not
in as bad a shape as you might think.
Choosing a versioning scheme is more
important than most programmers
really understand, in part because a
versioning scheme is a form of human
communication, and human commu-nication…well, let’s just say that many
programmers don’t get that at all.
A versioning scheme serves a few
important purposes. The most obvious
is allowing users to know where they
are in the evolution of your software,
but version numbers also communi-
cate a good deal more information.