MCBastos wrote:
Interviewed by CNN on 4/4/2010 14:41, Phillip Jones told the world:
Ant wrote:
On 4/4/2010 5:30 AM PT, Jens Hatlak typed:
Never. 2.1 will use Gecko 1.9.3. We're skipping Gecko 1.9.2.
Ah thanks! Any ETA on its public stable release?
We are just now at 2.0.4 and 2.0 came out in OCT. so four versions in 6
months means one about every 6 weeks. If that continues That will mean
another 36 weeks (6 times 6) or about 9 months. Just an educated guess
based on how its been tracking so far.
That's a faulty assumption. It implicitly assumes that there is
necessarily going to be a continuous sequence, including 2.0.4, 2.0.5,
2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.1.0. That's not how version numbers work
at all.
In fact, it breaks down in the following way:
x.y.z,
where
x: Major version. Expect big changes when this number changes. Example:
Seamonkey changed from XPFE to the Firefox toolkit when going from 1.x
to 2.x. Don't be surprised if some of those changes will break
compatibility in a big way with existing add-ons.
y: Minor version. Some change in functionality, but usually not as
visible. Compatibility breaks tend to be less common and more easily
fixed. Sometimes, more significant revisions that don't quite rate a
major version change will be represented by a large jump here -- like
the jump from Firefox 3.0 to 3.5.
z: Maintenance release. Bugfixs, mostly. No expected change in
functionality or compatibility.
(Some projects use four levels of version numbers)
Note that this is NOT a strictly decimal system -- that is, any of those
numbers can exceed one digit. Seamonkey 1.x, in fact, had as 1.1.19 as
its last version -- under your logic, you would expect 1.1.10 to be
called "1.2".
Also, there's no reason why the maintenance would have to reach the "9"
value before the minor version could be incremented. It might be that
Seamonkey goes from 2.0.7 to 2.1.0, for instance.
Best as I can remember we went through the .1 one progressions until
1.1.10 here they were .01 progressions where it was mostly patches for
security reasons not adding features, and working out bugs. SM-SM1.1.19
had been out for a at least 3-4 years. and before that was Mozilla.
Communicator was the last OS9 based Mozilla product usable on OS9 machines.
But you are right progression doesn't have to go in .1, or .01
Progressions. Tomorrow what we might consider 2.0.5 might end up 2.2
The choice of what a company calls their software is up to the company.
I was basing my assumption on how long SM 1 was around.
--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net http://www.vpea.org
mailto:[email protected]
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
