Enhancement #669
Updated by J. Moringen over 12 years ago
Since most build jobs have to be touched for the release of version 0.5 anyway, I would like to use this opportunity and rename all build jobs such that they conform to the following scheme
<pre>
rsb[-SUBPROJECT][-IMPLEMENTATIONLANGUAGE][-VERSION][-windows]
</pre>
where
* @IMPLEMENTATIONLANGUAGE@, if present, would be one of @cpp@, @java@, @python@, @cl@
* @VERSION@, if not trunk, would be something like @0.5@ (instead of @stable@)
* @-windows@ is appended if a separate build job is required for Windows
Sounds good?
Remaining issues:
* Only the trunk versions of rsb-{cpp,java,python} upload their generated documentation. Should we do this for 0.4, 0.5 as well?
* Update dependencies of "nao-cross-image job":http://ci.cor-lab.de/job/nao-cross-image/
<pre>
rsb[-SUBPROJECT][-IMPLEMENTATIONLANGUAGE][-VERSION][-windows]
</pre>
where
* @IMPLEMENTATIONLANGUAGE@, if present, would be one of @cpp@, @java@, @python@, @cl@
* @VERSION@, if not trunk, would be something like @0.5@ (instead of @stable@)
* @-windows@ is appended if a separate build job is required for Windows
Sounds good?
Remaining issues:
* Only the trunk versions of rsb-{cpp,java,python} upload their generated documentation. Should we do this for 0.4, 0.5 as well?
* Update dependencies of "nao-cross-image job":http://ci.cor-lab.de/job/nao-cross-image/