avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@d-haven.org>
Subject Re: Proposal: Versioning
Date Tue, 06 Apr 2004 12:55:13 GMT
Alex Karasulu wrote:
> Hi,
> +1 for following the Linux model to the T.
> My $0.02,
> Alex

So far, the only project to use it successfully is Linux.  Take for instance the
JEdit crew.  They have a feature that tells you if there is a more recent
update.  The only problem is that it does not discern between stable and
development versions.  They use the Linux model to the T so 4.1 is development
while 4.0 is stable.  The problem is that if you have a 4.0 release and 4.0.1
comes out, you will never know until you go to the site because the feature
that tells you if there is a new version always tells you the highest number--
which will be something like 4.1.13.

In other words, unless you only have one thing to download (like the linux
kernel), if you want to stay current you have to have something that can
tell the difference between a dev stream and a stable stream.

As far as Apache HTTPD goes, its version numbers simply increase.  When
something is ready to be released, they do an RC (release candidate).  If the
release candidate is golden, it becomes the full version.  However, if there is
a problem, the version is incremented and a new RC is made.  If you download a
version that does not have an RC designator, it is always a stable release.

It is easier to grasp than any version model that has more semantics built into
the numbering scheme.

For us, we basically adopted the HTTPD scheme and added one more level: the DEV
release for something that is unofficial, but being tested.  Our stuff has many 
libraries so there is not the concept of one download.

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message