Naming Conventions

This pages described the naming conventions for the data management components on the following aspects:

Terminology

• Major enhancements: new functionality is added to a component and the new functionality breaks the existing API contracts or changes the user interfaces. In this case a new release of the component is produced with a new version number incrementing the major version.
• Minor enhancements: new functionality is added to a component and the new functionality doesn’t break the API contracts or change the user interfaces. In this case a new release of the component is produced with a new version number incrementing the minor version.
• Patch: no new functionality is added. The only modifications are introduced in order to fix bugs. In this case a new release of the component is produced with a new version number incrementing the revision level.
• Revision: a modification of the ETICS configuration only (e.g. build command change, new dependencies, names, etc.). Also used for changes applied during the release as unstable and integration phases.

SVN Tags

Tags should be created with the following structure:

[component_name]_R_[major]_[minor]_[patch]

Is is recommended not to use the revision number in SVN tags.

Version Numbers

Version numbers are a combination of four numbers with the following structure:

[major].[minor].[patch]-[revision]

The revision added is added to the version number to reflect different builds and/or configurations.

ETICS Configurations

HEAD configurations have a fixed names which never changes:

[component_name].HEAD

Release configurations must follow the following convention (glite3.1):

[etics_component_name]_R_[major]_[minor]_[patch]_[revision]

Release configurations must follow the following convention (glite3.2):

[etics_component_name]_R_[major]_[minor]_[patch]_[revision]_GL32