| | 2 | |
| | 3 | == 2014/12/12 mail F. Maignan to orchidee-highlat@lists.lsce.ipsl.fr == |
| | 4 | Dear MICT developers, |
| | 5 | |
| | 6 | The IMBALANCE-P project will use the MICT branch as a starting point. |
| | 7 | We need to first clean the MICT branch, update it from the Trunk and include all MICT current developments that are not yet committed. |
| | 8 | |
| | 9 | To do this, we're building a small "MICT merge" working group, now including Shushi, Tao, Bertrand and myself (in close connection with Josefine). Feel free to join, we'll have weekly meetings on Friday, 11AM. |
| | 10 | |
| | 11 | To build a clean code that can be useful to all of us, here are the first guidelines that we propose: |
| | 12 | |
| | 13 | - The "MICT merge" working group does regular updates from the Trunk towards the MICT branch. |
| | 14 | |
| | 15 | - All people developing the MICT branch use a personal branch where they do their commits, respecting the Coding guidelines (particularly code documentation and parameters externalization). |
| | 16 | |
| | 17 | - These personal commits are then incrementally committed in the MICT branch. |
| | 18 | |
| | 19 | - These commits are planned by the "MICT merge" working group, discussed with Josefine and tested on a global scale resolution 2 degrees with a |
| | 20 | check on at least GPP and evapotranspiration. In case of a keyword, two tests with the option enabled then disabled are run. |
| | 21 | |
| | 22 | - Every MICT developer makes regular updates from the MICT branch towards its personal branch. |
| | 23 | |
| | 24 | - Tickets are used to report problems. |
| | 25 | |
| | 26 | - The MICT page of the wiki is used for reporting. |
| | 27 | |
| | 28 | - The orchidee-highlat@lists.lsce.ipsl.fr mailing list is used to disseminate information. |
| | 29 | |
| | 30 | |
| | 31 | Best regards,[[BR]] |
| | 32 | Fabienne, in behalf of the "MICT merge" working group |
| | 33 | |
