| Version 5 (modified by ajornet, 9 years ago) (diff) |
|---|
Branch ORCHIDEE-MICT-IMBALANCE-P
Coding Guidelines
- Respect the general ORCHIDEE coding guidelines
- Every MICT developer uses a personal branch where s/he does his/her commits.
- Every new development is protected by a KEYWORD to allow easy testing with or without the new option.
Pages
2014/12/12 mail F. Maignan to orchidee-highlat@…
Dear MICT developers,
The IMBALANCE-P project will use the MICT branch as a starting point. We need to first clean the MICT branch, update it from the Trunk and include all MICT current developments that are not yet committed.
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.
To build a clean code that can be useful to all of us, here are the first guidelines that we propose:
- The "MICT merge" working group does regular updates from the Trunk towards the MICT branch.
- 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).
- These personal commits are then incrementally committed in the MICT branch.
- These commits are planned by the "MICT merge" working group, discussed with Josefine and tested on a global scale resolution 2 degrees with a
check on at least GPP and evapotranspiration. In case of a keyword, two tests with the option enabled then disabled are run.
- Every MICT developer makes regular updates from the MICT branch towards its personal branch.
- Tickets are used to report problems.
- The MICT page of the wiki is used for reporting.
- The orchidee-highlat@… mailing list is used to disseminate information.
Best regards,
Fabienne, in behalf of the "MICT merge" working group
