| 2 | |
| 3 | === 17/11/2010 === |
| 4 | Presentation of the new versioning system '''svn''' by Martial Mancip [[BR]] [[BR]] |
| 5 | 1 - Design (see https://forge.ipsl.jussieu.fr/orchidee/browser) [[BR]] |
| 6 | * The '''tag''' directory was first created by importing the last cvs 1_9_5 tag (AR5 version) including both ORCHIDEE and ORCHIDEE_OL (meaning source code, scripts, diagnostics and documentation). [[BR]] |
| 7 | * The '''trunk''' directory was then created by copying this first tag. This directory represents the current version under development and is to be tagged when ready. [[BR]] |
| 8 | * The '''branches''' directory will include separately the major on-going developments (nitrogen, phenology, assimilation, ...). When ready, they will be merged into the trunk directory. [[BR]] |
| 9 | * The '''perso''' directory will include separately all developments made by students and post-docts. [[BR]] |
| 10 | * Note that the release number is globally incremented each time any file is modified (this is a major difference from cvs). [[BR]] |
| 11 | * Click on '''Revtree''' (upper right) to visualize the Revision Tree and see the model evolution (select options then click on 'Update'). [[BR]] |
| 12 | 2 - Project Management Tools (labels 'See Tickets', 'New Ticket', 'Roadmap', 'Timeline') [[BR]] |
| 13 | * A '''New Ticket''' is created each time an action is required (bug to resolve, new branch to create, enhancement required, ...). [[BR]] |
| 14 | * Tickets are associated to '''Milestones''', defining the main objectives we are currently trying to reach. [[BR]] |
| 15 | * ''Tickets are listed and discussed every two weeks during the technical meetings.'' [[BR]] |
| 16 | * The '''Roadmap''' enables to visualize the different Milestones completion. [[BR]] |
| 17 | 3 - Authorizations [[BR]] |
| 18 | * Each '''user''' will have a wiki login and password. [[BR]] |
| 19 | * Already existing '''group'''s are admin (Martial Mancip, Nicolas Vuichard, Didier Solyga, Fabienne Maignan) and users. A group can be created for each corresponding branch (e.g. assim, pheno). |
| 20 | * ''Trunk commits are decided within the orchidee projects meetings.'' [[BR]] |
| 21 | 4 - Next actions [[BR]] |
| 22 | * Decide which commits are sent by e-mail to which list. [[BR]] |
| 23 | * Foresee another technical meeting to declare Milestones, create branches, ... [[BR]] |