Changes between Version 12 and Version 13 of Developers/DevelopingCodeChanges

Timestamp:

2016-01-14T10:38:23+01:00 (8 years ago)

Author:

clevy

Comment:

--

Developers/DevelopingCodeChanges

@@ -5 +5 @@
 
 ----
+== '''History''' ==
+Until end of 2015,  the PI if a given development action was expected to develop the code and its documentation in a development branch, to go through the different validation steps, and to submit it at the end to a reviewer, the positive answer of the review being a prerequisite for a merge into the NEMO reference. [[BR]]Since Merge Party meeting end of 2015, the process has been changed to a more efficent and reliable process, in order to avoid disagreement and a lock at the review step. The sequence described below is presently to be followed for each development of the NEMO System Team's workplan.
+
 '''A brief overview of the process is given below:'''
 
- 1. !''Plan your change!'''
- 1. !'''Create a Ticket!'''. The ticket is used to document the change and review status.
+ 1. Workplan content: Each development action is expected to be described in the yearly workplan
+ 1. Detailed description of tasks and Preview step
  1. !'''Create a Branch!'''. The branch is a copy of the code that will be used to develop your change.
  1. !'''Develop your Change!'''. Checkout your branch base code, develop and commit changes to your branch.
@@ -17 +20 @@
 Merging back with the trunk is not described here.
 
-== Plan Your Change ==
-A discussion at an early stage with the NEMO Systems team/code owners should help make sure your change is viable, desirable and as easy as possible.
+== Workplan content ==
+The yearly workplan is discussed within System Team, submitted to Developer's Committee, and approved by Steering Committee. It must include, for each development action, its motivation, status, main tasks so as a PI name, and a previewer (which will also be the reviewer) name. If needed, previewer can be divided into a "Science Previewer" and a "System Previewer". The name of Previewer should be added only once he did accept the task, and before submission of workplan to Developer's Committee.[[BR]]
 
-== Create a Ticket ==
-When a code change is being planned a ticket should be created describing the purpose of the change. The other fields in the ticket (e.g. Priority, Milestone, Keywords etc) should also be set appropriately.
+== Detailed description of tasks and Preview step ==
+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 an associated wiki page using the template (to be created). 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 !''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 at this stage.
+ * The ticket should be assigned to the code developer and the previewer at this stage.
+
+The wiki page will describe:
+
+ * Purpose and associated action number on workplan
+ * Motivation
+ * Status
+ * Main tasks
+ * Pi name
+ * Previewer(s) name
+ * Detailed implementation plan (scientific and technical): this is also expected to be used as summary of changes to NEMO reference manual to be written later
+
+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).
 
 == Create a Branch ==