Changes between Version 44 and Version 45 of Developers/DevProcess

Timestamp:

2016-02-25T17:43:43+01:00 (8 years ago)

Author:

nicolasmartin

Comment:

--

Developers/DevProcess

@@ -2 +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.
 
-[[PageOutline(2)]]
+[[PageOutline(2,,inline)]]
 
 Color code for the fulfilment:
-||
-{{{
-#!td style="background:lightgrey"
-'''PI(S)'''
+{{{#!th align=left
+1. [#abstract Abstract]
 }}}
-||
-{{{
-#!td style="background:lightblue"
-'''Previewer(s)'''
+{{{#!td style="background:lightgrey"
+PI(S)
 }}}
-||
-{{{
-#!td style="background:lightgreen"
-'''Reviewer(s)'''
+|-
+{{{#!th align=left
+2. [#preview Preview]
 }}}
-== Abstract ==
+{{{#!td style="background:lightblue"
+Previewers
+}}}
+|-
+{{{#!th align=left
+3. [#tests Tests]
+}}}
+{{{#!td style="background:lightgrey"
+PI(S)
+}}}
+|-
+{{{#!th align=left
+4. [#review Review]
+}}}
+{{{#!td style="background:lightgreen"
+Reviewers
+}}}
+
+== Abstract == #abstract
 This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.
 
@@ -30 +43 @@
 || Action || ''[tf.input:action -id=piform 'Number & name' 100]'' ||
 || PI(S) || ''[tf.input:pi -id=piform 'Names' 100]'' ||
-|| Linked !ticket || ''[tf.input:ticket -id=piform #]'' ||
+|-
+{{{
+#!th align=left
+Ticket
+}}}
+{{{
+#!td style="background:lightgrey"
+''#XXXX''
+}}}
+|-
+{{{
+#!th align=left
+Branch
+}}}
+{{{
+#!td style="background:lightgrey"
+''#XXXX''
+}}}
+|-
 || Previewer(s) || ''[tf.input:previewers -id=piform 'Names' 100]'' ||
 || Reviewer(s) || ''[tf.input:reviewers -id=piform 'Names' 100]'' ||
@@ -41 +72 @@
 ==== ''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 ==
+== Preview == #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.
 
@@ -59 +89 @@
 ==== ''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 ==
+== Tests == #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.
 
@@ -83 +112 @@
 ==== ''Updated on [tf.form_updated_on:] by [tf.form_updater:]'' ====
 }}}
-
-== Review ==
+== Review == #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).
 
@@ -107 +135 @@
 ==== ''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.