Merge with main/production branch and policy for such merges
As we now have production running on https://marketplace.sshopencloud.eu we should think about updating the backend code for this instance. By merging to the master-branch the CI/CD pipeline will update the production code. Before, we should discuss when to do this.
First of all we need to take into account, that a full re-index of Solr would lead to around 4 hours where the production instance will not give results for search endpoints. I'm not sure under which circumstances such a re-index of Solr happens, see #148 (closed) for further discussion on this.
Secondly, we should also think about a policy when such updates for production should happen. I guess we like to test new features on stage/develop before pushing them to production. Who will do this tests and where do we collect the information so that someone can decide to push to the master-branch? What is the policy on this?
Asking @matej.durco @ekalata @tparkola @lbarbot @edward.gray