New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
2016WP/ROBUST-10_MARTIN (diff) – NEMO

Changes between Version 5 and Version 6 of 2016WP/ROBUST-10_MARTIN


Ignore:
Timestamp:
2016-04-06T11:40:48+02:00 (8 years ago)
Author:
acc
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 2016WP/ROBUST-10_MARTIN

    v5 v6  
    9494== Preview == 
    9595 
     96=== Preview discussions === 
     97 
     98{{{#!td 
     99Comments from Previewer 1: Andrew Coward: 
     100 
     101The task description and background context is well explained and the implementation plan appears to be well formulated. However, this is a difficult plan for 
     102system team officers to preview  since we are, at best, 'knowledgable users' of the Source Code Management and TRAC systems and we have 
     103little experience of installing and configuring them. I am happy to rely on Nicolas' expertise for that but it is clear that we must all contribute to content 
     104and design decisions at some stages. The plan, as written, lacks clarity as to when critical points will be reached that require collective effort. I suggest adding a Gantt chart with the best estimates of when tasks will be completed and showing when greater involvement from the system team may be necessary. This will help NEMO officers to schedule 
     105their commitments accordingly. 
     106 
     107Is there an opportunity here to ensure that the new system is more compatible with FCM so that we can avoid all the 'property change' commits that plague the current 
     108system? Does anyone have ideas how to do that? 
     109 
     110Also, it would be good to remove the reference manual PDF from any commits but have it rebuilt automatically if anything in DOC is changed. Can we add hook scripts to 
     111do that? 
     112 
     113}}} 
    96114Since 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. 
    97115