Bruce has mentioned that he didn’t understand the files on the good-day server in a comment to a prior blog post.
I’ll try to make this as simple as possible for end users to understand using the following example:
This can be broken down into several smaller chunks _ is used as a separator:
OOo is the short product name. Other options are BrOo (the Brazilian localisation of OpenOffice.org due to
SRC680 is the code line, this changes with every major release. All release candidates are done on a different code line. For example OpenOffice.org 2.3.x used OOG680.
m237 is the milestone. OpenOffice.org code base has a new milestone every few weeks (sometimes a milestone will have only a few days between but this is rare). This number increases after several new code change have been integrated into the trunk of the code line. Internally within OpenOffice.org this is a MWS or Master WorkSpace.*
MacOSXIntel tells you the Operating System and the Platform that this build is for. Another option relevant to mac users is MacOSXPPC or MacOSXPowerPC. The name is changing/has changed to come in line with other platforms.
AQUA states that this is an AQUA build. The other option is X11. This option is only there during the transition from X11 to Aqua. It will be soon be the case that this parameter won’t be included when Aqua is default.
install is there to say that this is an application and not a language pack, SDK or URE. The SDK and URE are generally only needed by developers. Language packs are currently not available for Mac OS X.
en-US this is the language that is to be installed.
* In OpenOffice.org we use a trunk and branch method. Think of a tree growing. Any new code is created in a branch (internally called a CWS), which is merged back into the trunk when it is ready. Think of the milestones being the rings you see when you cut a tree down. However we are producing these rings (milestones) far more frequently than a tree in nature.