Changes between Version 17 and Version 18 of Developers/DevelopingCodeChanges

Timestamp:

2016-02-02T11:49:17+01:00 (8 years ago)

Author:

clevy

Comment:

--

Developers/DevelopingCodeChanges

@@ -15 +15 @@
  1. !'''Develop your Change!'''. Checkout your branch base code, develop and commit changes to your branch.
  1. !'''Test your Change!'''. Make sure you test your changes adequately.
- 1. !'''Document your Change!'''. Update your ticket with all the information that another user/developer might need.
+ 1. !'''Document your Change!'''. Update your !ticket with all the information that another user/developer might need.
  1. !'''Science/Tech/Code Review!'''. Review of the change by an expert on the scientific or technical area you are changing and for adherence to coding standards.
 
@@ -26 +26 @@
 Once the workplan has been approved, the code development is planned. The PI should
 
- * create a ticket to start the work. This ticket will describe the purpose of the action, so as Pi and Previewer name.
+ * create a !ticket to start the work. This ticket will describe the purpose of the action, so as Pi and Previewer name.
  * Create 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 wiki page will permit to follow the ongoing work through different steps. The wiki page will be linked to the ticket.
 
-The other fields in the ticket (e.g. Priority, Milestone, Keywords etc) should also be set appropriately.
+The other fields in the !ticket (e.g. Priority, Milestone, Keywords etc) should also be set appropriately.
 
  * The !''milestone!'' field should be set to the area the change is being targeted for.
  * The ticket !''type!'' field should be set to "development branch"
- * Associated wiki page should be created by including the markup !wiki:ticket/xxxx (where xxxx is your ticket number) in your ticket and then following the link.
- * The ticket should be assigned to the code developer and the previewer at this stage.
+ * Associated wiki page should be created by including the markup !wiki:ticket/xxxx (where xxxx is your ticket number) in your !ticket and then following the link.
+ * The !ticket should be assigned to the code developer and the previewer at this stage.
 
 The wiki page will describe:
@@ -69 +69 @@
 
 === Document your Change ===
- * Progress in the development should be documented as the work goes on in the ticket created at the beginning/
+ * Progress in the development should be documented as the work goes on in the !ticket created at the beginning/
  * Code should be documented on line as defined in the coding rules
  * Changes in the reference manual should be also written as soon as possible, and before review process