Changes between Version 5 and Version 6 of 2016WP/ROBUST-10_MARTIN
- Timestamp:
- 2016-04-06T11:40:48+02:00 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2016WP/ROBUST-10_MARTIN
v5 v6 94 94 == Preview == 95 95 96 === Preview discussions === 97 98 {{{#!td 99 Comments from Previewer 1: Andrew Coward: 100 101 The task description and background context is well explained and the implementation plan appears to be well formulated. However, this is a difficult plan for 102 system team officers to preview since we are, at best, 'knowledgable users' of the Source Code Management and TRAC systems and we have 103 little 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 104 and 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 105 their commitments accordingly. 106 107 Is 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 108 system? Does anyone have ideas how to do that? 109 110 Also, 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 111 do that? 112 113 }}} 96 114 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. 97 115