...

Please note that module system allows to provide defaults on every level of module structure. So, taking imasenv as an example there is :

• default DD for module imasenv  
• default UAL for module imasenv/<DD_ver> 
• default set of libraries submodules for module imasenv/<DD_ver>/ual/<UAL_ver> 
• etc, etc

...

"WPCD products"

ETS workflow is the most complex product being developed by WPCD, however WPCD activity is not limited to ETS development, so this document will refer to "WPCD products" keeping in mind that in most cases it is synonym of "ERTS workflow"

Lifecycle

Tagged version

• Tagged version of module, used by some tagged version(s) of  CD product(s)
• Must be well tested  and stable 
• This version is intended to use mainly by users , to provide them stable environment for running  CD product(s) 
• The chosen tagged version (in most cases the latest one) is set as default  

Release candidate (RC)

• A candidate for a next tagged version
• Provides a common, unified environment for developers working on next version of given CD product 
• A RC version should be stable, however it would be changed quite often (patches, new functionality of libraries) so it may happen that RC version will have some issues
• Once WPCD confirms that its product works fine, RC is tagged 

Alpha version

• A candidate for a next tagged version
• Introduced to make sure that update/change requested by developer(s) is "safe"  and will not brake environment (used by large group of developers)
• Used by a limited group of testers (usually person who request change)
• If tests are passed, changes are introduced to RC:
  • patches automatically
  • library updates (that may change APIs) after confirmation coming from WPCD