That repository aims to handle a commom Kohinos code for the local currency that take part in the mutualization (and found it).
Our code if free, so that local currencies don't want to fit in the previsous rules can freely fork this Github repository. However, we higly encourage then to not fork the common modules. In that case it would be very difficult for them to entrer in the mutualization in the future.
Upgrading process
============
Step A : on the DEV environnement
-------------
=> Developper for or repo and creates a branch from our production branch
=> Developper commit changes on his own repo
=> Developper make a PR to the DEV branch : he adds to the description :
- a link to the ticket (and he adds the link of the PR to the ticket)
- the module name we have to update
- the module name we have to install
He adds the PR link to the TMS ticket.
=> The repo management team checks the code, and merge the PR against DEV branch
=> The hosting team update the code on staging instance, restore the lastest nighly DB copy. They set the ticket to "on dev" status and send a message to users to describe the changes (basicly a screenshot of the ticket list that have be solved).
Step B : on the PROD environnement
-------------
Once the test are conpleted, the repo management team merge DEV -> production branch.
=> The hosting team update the code on staging instance, install/uninstall/update module dans execute migration scripts. They set the ticket to "on prod" status and send a message to users to describe the changes (basicly a screenshot of the ticket list that have be solved).
=> If the module is generic (inside the OCA repository), the developper create a PR against OCA repo
