Changes between Version 25 and Version 26 of Developers/DevelopingCodeChanges

Timestamp:

2016-02-24T10:00:10+01:00 (8 years ago)

Author:

clevy

Comment:

--

Developers/DevelopingCodeChanges

@@ -31 +31 @@
 
  * A !ticket to start the work. This !ticket will describe the purpose of the action, so as Pi and Previewer name.
- * An associated wiki page using the [http://forge.ipsl.jussieu.fr/nemo/wiki/PageTemplates/NEMO_Devlt_Preview_and_ReviewTemplate development preview and review template]. This page will permit to follow the ongoing work through different steps and will be linked to the !ticket.
+ * An associated wiki page using the [http://forge.ipsl.jussieu.fr/nemo/wiki/PageTemplates/NEMO_Devlt_Preview_and_ReviewTemplate development preview and review template]. This page will permit to follow the ongoing work through different steps and will be linked to the !ticket. IMPORTANT: you need to create the wiki page, withi appropraite name, using the template (you do not have write access to the template itself).
 
 The other fields in the !ticket (e.g. Priority, Milestone, Keywords etc) should also be set appropriately.
@@ -52 +52 @@
 
 Once the wiki page is completed by PI (detailed implementation plan), the PI will submit it to Previewer. The Previewer will discuss with PI to reach full agreement on detailed implementation plan (in a maximum of 2 weeks starting when PI submits wiki page to Previewer).[[BR]]The PI is responsible to give all requested details.[[BR]]The Previewer is responsible to check with all experts that implementation plan is indeed coorect and compatible with the other developments going on in parallel during the year.  Objective is to avoid the need for a full rewriting at the end (which did happen sometimes previously)
+
 == Start the coding ==
 Once the Previewer has sent the green light (approval of detailed implementation plan and summary of changes in reference manual), the PI can created the corresponding  development branch. The branch should be created from the up to date version of NEMO as chosen for each year (usually the trunk at a give fixed revision for a give year, see minutes of NEMO System Team videoconferences.  Development can progress on this new branch.
@@ -71 +72 @@
 
 ''In particular the Trusting tool has been developed in order to ease the validation all along the working on the code, not all in one with SETTE. The developer can regularly evaluate the changes for a any given configuration compared with benchmark results he has defined.''
+
 === Document your Change ===
  * Progress in the development should be documented as the work goes on in the !ticket created at the beginning/