Glossary is always updated to the latest master on deploy

[skalee]

Although we use Git submodules for tracking version of the glossary, both build and deploy scripts always attempt to update the glossary by executing make update-modules, which is equivalent to git submodule foreach git pull origin master.

That means that any change pushed to the master branch of https://github.com/geolexica/isotc211-glossary will go live next time site is deployed. Glossary development becomes tightly coupled with site development. This will cause problems when we decide to hold on with releasing new glossary for whatever reason (breaking changes, bugs, pending reviews, etc.). We can't even deploy a tiny bugfix without deploying glossary updates.

That wasn't a problem before. Ongoing glossary development was happening in spreadsheets. New commits in isotc211-glossary repo were occasional, they were resulting either from of spreadsheet release or parser release. Now it seems different.

So — what to do, @ronaldtse, @strogonoff?

[ronaldtse]

1. The goal is to eventually allow the app to directly deploy the website.
2. Updates to the repo will be more frequent from now on since the release mechanism is now changed from spreadsheet release to change requests via the app. We need to enable some test/gating method so that the site doesn't break even if the data breaks, and enable some tests so that the data doesn't break.

[skalee]

Perhaps we should deploy the latest release rather than current master?

[ronaldtse]

Maybe, we could bind the release to the latest approved change request? Thoughts @strogonoff ?