Version the template

[jorgemoralespou]

If there is a schema to version launchpad and the images, the template should also be versioned.

[quintesse]

And where would one normally put that version?

[gastaldi]

The idea is to move our launchpad to DevTools OSD, and they have their own CI process, as explained here: fabric8-launcher/launcher-planning#37

So as far as I understand, the version should be specified in a IMAGE_TAG env var, but I could be wrong

[jorgemoralespou]

There's 2 versions really when talking about templates:

• The version for the template, so that you can identify at any moment if you have the latest, and if there's changes in the template compatible/incompatible with the software.
• The version of the application (image/images).

You can align the version of the template and the images, so that a template x.y.z always deploys versions x.y.z of the application or a fixed combination (a.b.c for app1, and e.f.g for app2 and m.n.o of app3). In this case, if you release a new version of app1 or app2 or app3 or a combination of them, you'll update the template with the new versions for those apps, and version the template.

Another option is to have the template open, so that a user can specify which versions of app1, app2 and app3 wants to deploy.

A middle solution can be using the second approach and limiting in the parameters, which versions can be applied, so that you can for example, deploy different combinations of minor versions (e.g a.b.1, a.b.2, a.b.9) but no (a.x.1)

All this versioning thing needs to be done on the release process, which is what vaclav pavlin does.