Add ability to track production release

[thomasneirynck]

The current workflow to publish data does not allow to track which commit is actually published into production.

• the latest master is published to staging
• publishing to production is a separate jenkins job

We should be able to tie this to an actual commit. e.g. we could tag that commit, something with "currrent", or "production", or whatever.

The current workflow also causes another (related) problem:

We cannot patch EMS-file service without risking to publish staged data that is not ready for production.

An example of this the following situation

• EMS is publishing layers A, B, C in production
• we add layer X and merge into master
• we realize layer X contains mistakes so we do not publish master to production
• a bug is uncovered in data of layer A
  --> we cannot fix this bug and publish master to production, without removing layer X

The latter is an example of the situation where we are as of today with the 2nd level admin layer.

I'm happy to create a separate issue for the 2nd problem, but hopefully we can fix this together since the problem domain seem related.

[jsanz]

Staging deployment comes from feature-layers branch.

As for #171 we should have merged that against feature-layers, right? I understand we can now branch master to continue working on that dataset there, and revert master to the previous commit.

Nevertheless, I agree we should revisit the whole procedure; from git branches to the staging environment, and release. Publishing from annotated tags with associated descriptions and entry in the Releases Github tab would be an improvement.

[thomasneirynck]

Staging deployment comes from feature-layers branch.

ok thanks. I'm behind on this.

I agree we should revisit the whole procedure;

+1