| Version 1 (modified by smasson, 6 years ago) (diff) |
|---|
HPC-09_ESIWACE
The action has to be detailed briefly in the 'Summary' for later inclusion in other pages.
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.
Summary
| Action | HPC-09_ESIWACE |
|---|---|
| PI(S) | Maisonnave ATOS |
Digest | improve HPC performances |
| Dependencies | |
| Expected for | |
| Ticket | #0000 |
| Branch | NEMO/branches/$YEAR/dev_r{REV}_{ACTION_NAME} |
| Previewer(s) | |
| Reviewer(s) | |
| Link | ExtractUrl(.)? |
Abstract
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.
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.
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.
Review
Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.
