PerfSONAR product naming convention
From GEANT2-JRA1 Wiki
[edit]
Product Naming scheme
The following are the criteria for defining a perfSONAR product name
- Should be uniquely identifable
- Must include unique project name
- Could include category e.g. rrdma or ls
[edit]
The naming convention
- Every name should contain two parts, separated by an _ (underscore)
$name = $string1_$string2
- Every product release should contain the product name as well as the version, separated by an _ (underscore)
$release_name= $name_$version
- Where:
- $string1 has to be Organisation specific name (has to be unique across all organisations)
- $string2 has to be Project/Software specific name (example: -JAVA-RRD-MA, HADES-MA, BWCTL-MP, etc)
- $version (we are talking about 'per service' version here) has to be managed by the team doing the development and the release of the service/software
- Underscore required between projectname and the latter part
- Version number could be added to tar file or release tag
- Examples
- Names: GEANT2_JAVA-RRD-MA, GEANT2_PERL-HADES-MA
- Releases: GEANT2_JAVA-RRDMA_1.0, GEANT2_PERL-HADES-MA_0.2
