Automatic release process

Have tooling both to allow a single release to be made automatically, without having to manually update the versions in the POMs. Organize the versions in the POMs so they are in as few places as possible.

Have additional tooling to be able to release each component family separately, as well as the TCOMP modules and commons.

Documentation

Release scenario is described here https://wiki.talend.com/display/rd/Release+process

Requirements

1. We should be able to release component families separately. Component families may have different versions
2. We should be able to release TCOMP sdk separately from components (also service)
3. We should have a tool (script) for automatic release
4. Each release commit should be marked with tag. So, we need some tag naming convention to distinguish different versions and products

Subtasks

1. Define release commit and tag naming conventions
2. Discuss/decide about branching conventions for maintenance/bugfix
3. Discuss/decide about releasing components family separetely
4. Discuss/decide about changes to workflow (see below)
5. Check how to create branch for new development version
6. Setup maven release plugin for all "products"
7. Setup Jenkins job for release; teach developer and release maker

Component bugfix workflow draft

1. Create a branch for new development version for bugfix (0.1.0 -> 0.1.1-SNAPSHOT)
2. Make bugfix
3. Test bugfix
4. Make more bugfixed (repeat prev steps for each bugfix)
5. Release new component version for bugfix: 0.1.1-SNAPSHOT -> 0.1.1; make a tag; remove development branch (or leave it if we agree to have a lot of maintenance branches for each comp)
6. Upgrade component version in products (particularly, in Studio)