[Gllug] Mozilla on Redhat 7.1

[Simon Stewart]

On Wed, Aug 08, 2001 at 11:42:00AM +0100, Brent Geach wrote:
>
> Normally I've seen that
> 1st number = major release
> 2nd	   = minor code changes
> 3rd	   = bug fixes and patches
> 
> the beta and alpha releases usually have a b or a at the end.
> I may be wrong though, but this is the algorithum I've always understood it to be.
 
Ahhh... this is where the chaos kicks in: a rule of thumb is that if
the 2nd number is odd then you're using a testing or unstable release,
but if it's even then you're using a production release (think linux
kernel)

But this doesn't always work: look at Apache, for example --- the most
recent stable release is 1.3.19 (or thereabouts ;) --- or the old Perl
numbering scheme (which has now changed)

To make things even nicer, some people do "alpha", "beta" and "release
candidate" releases, while others do nightly builds, which may be of
alpha, beta or RC quality by their very nature.

Personally, I'm waiting for someone to do an Icarus release (use it
and you may get burnt and crash horribly) and a Daedelus release (old,
steady, should work properly) :))

Cheers,

Simon

-- 
"I have a longstanding agreement with tequila: I won't
 drink it, and it won't make me sick."  -- Brian Kantor


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug