Provide a standard for release variants

---- rudylattae (2008-11-29)
Here is my suggestion for release variants:

* Normal (no prefix): a usable release with all packages and meta data minus the intro and spaces. May be used in standalone/embedded development/production scenarios.
* Compact ("compact_" prefix): a usable release with only the style package and meta data minus all other packages that do not house internal resources (images, etc.). The intro and spaces will also be excluded. The directories for any packages that have internal resources (like background images, etc.) will be kept but stripped of any stylesheets that are already available as combo+mini in the style package. May be used in embedded production scenarios where the theme designer/developer will have no need to reference sub packages specifically. It is meant to have a small footprint and through style combo+mini would cause less hits to the server and consume less bandwidth.
* Full ("full_" prefix): a usable release with all packages, intro and meta data minus the spaces. May be used in standalone/embedded development/production scenarios.
* Source ("src_" prefix): the entire source repository including all packages, intro, meta data and spaces.

Terminology:
* Package: internal grouping of stylesheets, images and other resources used in the main project (e.g. core, context, debug, etc...)
* Style package: a special package ("style") that contains (usually) both raw and combo+mini versions of the other style packages in the theme.
* Intro: usually a start page (index.html) and related resources (sub pages, stylesheets, scripts, images, etc.)
* Meta data: dirs (_fs, _nfo, etc.) and files (README.txt, LICENSE.txt, etc.) that contain meta data or additional files for the project. Dir is prefixed with "_" (underscore)
* Space: self contained project space (__test, __doc, etc.) that is actually stored in the main project space. Directory (dir) name is prefixed with "__" (double underscore)