Hi Lihua,
OOA680 = 1. Update for OOo 2.0
OOB680 = 2. Update for OOo 2.0
In European languages it is common to use the alphabet to
describe a numbering.
A = 1.
B = 2.
....
In between the release cycle of OOo 2.x it was changed that OOo was
released as Feature release (e.g. 2.3) or only Bugfix release
(e.g. 2.3.1). The bugfix releases are on the same code base like the
corresponding feature release.
---- OOo 2.3.1 (OOG...)---| --- OOo 2.4.1 (OOH...) --
/ /
- OOo 2.3 -|--------------------- OOo 2.4 ---|
But now there will not be any development on OOo 2.x code base anymore.
When security fixes or major bug fixes are needed, there will be a
OOo 2.4.2, which will base on the code line of OOo 2.4.1. So the fixes
will be done on OOH680_mX.
So there isn't a plan for 2.5, 2.6 or any other feature releases on 2.x.
The limitation of the naming of the code base is 3 characters (OO?) and
3 numbers (680).
The naming BEA if for 1. Beta (BE = Beta, A = 1.). So the naming BEB
is for the 2. Beta (BE = Beta, B = 2). I do not know the naming for
the 3.0 final, but it will be like OOA300 or something like that.
Thorsten
Zhu Lihua wrote:
> Hi all,
>
> I know OOo2.2 is corresponding to OOF680_mX, OOo2.3 is corresponding to
> OOG680_mX, OOo2.4 is corresponding to OOH680_mX.
>
> What's the name of "OOF680_mX, OOG680_mX, ..."? Version? I think OOo2.X are
> more like a Version. OOo2.X and OOX680_mX must
> have different names. What are they?
>
> For the OOo3.0, I knew DEV300_mX is corresponding with OOo3.X. But now I've
> noticed that BEA300 and BEB300 appeared. What's
> the relationship between DEV and BEA?
>
> Thank you!
>
>
> Best regards,
> Lihua
>
>
>
>
> 2008-07-08
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
