Discussion about consistent tagging of toolkit code and test artifacts

[joergboe]

Toolkits contain besides of the toolkit code other components which are:

• samples
• checked in documentation artifacts (this is not the generated spl-doc or java-doc etc)
• test components When a toolkit is released, a tag is applied and the toolkit tests are initiated. But very often it turns out that the toolkit code is fine, but there are changes in the test components required. Thre are several ways to handle this:
  1. Remove the old tag and apply the label on the corrected checkin (bad practice, confusing and may break remote workspaces)
  2. Create a maintenance branch from the original label, implement the required changes, merge them into the main development branch and add a new label in the form vx.y.z_update1. Where the original label vx.y.z and the update contain the same toolkit code
  3. Separate the test folder from the rest of the toolkit code and put it into a separate repository

[ddebrunner]

Not sure what the problem is exactly. Shouldn't the tests be run and passing before a release is made?