Changes between Version 58 and Version 59 of Developers/DevProcess

Timestamp:

2016-03-04T00:45:17+01:00 (8 years ago)

Author:

nicolasmartin

Comment:

--

Developers/DevProcess

@@ -1 +1 @@
 = Form page for development work =
 
-A wiki page associated with a give action should be created in `wiki/${YEAR}WP/${WORKING_GROUP}-${ACTION_NUMBER}_${PI}` using this template.[[BR]] From that, you can customize it while editing within the !TracForm container `{{{#!TracForm ... }}}`. If necessary, you can copy the entire form (add a number `_[0-9]` to wiki page name) or the respective area in order to match the number of the (P)Reviewer(s). The best solution is not to extend significantly the length of the page.
+A wiki page associated with a give action should be created in `wiki/${YEAR}WP/${WORKING_GROUP}-${ACTION_NUMBER}_${PI}` using this template.[[BR]]From that, you can customize it while editing within the !TracForm container `{{{#!TracForm ... }}}`. If necessary, you can copy the entire form (add a number `_[0-9]` to wiki page name) or the respective area in order to match the number of the (P)Reviewer(s). The best solution is not to extend significantly the length of the page.
 
 This is the color code for the fulfilment of this form:
@@ -16 +16 @@
 
 ----
+
 [[PageOutline(2)]]
+
 The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.[[BR]]
 
 == Abstract ==
+
 This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.
 
@@ -41 +44 @@
 === Reference manual updates ===
  [tf.textarea:manual -id=piform 'Using part 1 and 2, define the summary of changes to be done in the NEMO reference manual (tex files).' 200 20]
+
 '''Updated on [tf.form_updated_on:] by [tf.form_updater:]'''
 }}}
+
 Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.
+
 == Preview ==
+
 Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request.[[BR]]For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions.
 
@@ -57 +64 @@
 || Does the previewer agree with the proposed summary of updates in reference manual? || [tf.select:2.4 -id=preform '' Yes No NR] || [tf.textarea:2.4 -id=preform 'Add a comment?' 50 10] ||
 || ... ... ... || [tf.select:2.X -id=preform '' Yes No NR] || [tf.textarea:2.X -id=preform 'Add a comment?' 50 10] ||
+
 '''Updated on [tf.form_updated_on:] by [tf.form_updater:]'''
 }}}
+
 Once all "YES" have been reached, the PI can start the development into his development branch.
+
 == Tests ==
+
 Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section.
 
@@ -79 +90 @@
 || Are there significant changes in run time/memory? || [tf.select:3.10 -id=piform '' Yes No NR] || [tf.textarea:3.10 -id=piform 'Add a comment?' 50 10] ||
 || ... ... ... || [tf.select:3.XX -id=piform '' Yes No NR] || [tf.textarea:3.XX -id=piform 'Add a comment?' 50 10] ||
+
 '''Updated on [tf.form_updated_on:] by [tf.form_updater:]'''
 }}}
+
 == Review ==
+
 A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).
 
@@ -105 +119 @@
 '''Updated on [tf.form_updated_on:] by [tf.form_updater:]'''
 }}}
+
 Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.