JRA1 Deliverable Review Form
Identification of the deliverable or milestone |
Project: EMI |
Deliverable or milestone identifier: D3.2 |
Title: DSA1.2 - Software Release Plan |
Doc. identifier: EMI-DSA1.2-CDSREF-Software_Release_Plan-v0.14.doc |
Author(s): C. Aiftimiei |
Due date: 17/01/11 |
Identification of the reviewer |
Name: M. Riedel |
Affiliation: JUELICH |
EMI Activity/External project or Institute: JRA1 |
Review date |
2011-01-17 |
Author(s) revision date |
mm/dd/yyyy |
Reviewer acceptance date |
mm/dd/yyyy |
Attach the reviewed document to the deliverable page, put here a link
General comments
Very good document. Perhaps sometimes the long sentences or indications of copy&paste (from wikis) can be refined (minor).
M. Riedel 27/01/11:
with thanks to Cristina I confirm that my comments where fruitfully addressed.
In addition, I would vote to distribute it broadly in the project as well as in the community:
(1)
Once this document is fully approved, I recommend it should find its way to EGI (e.g. Michel) being one of our major customers in
order to receive detailed comments.
This enables us to potentially synchronize and to get more concrete feedback about the 'divergence' of EMI-EGI release procedures we
heard recently.
I believe the EC would not really appreciate when our release procedures are not in-line with them.
Although we might not be able to change for EMI-1 of course we need to discuss this but I got the feeling that this is already
happening in the TCB.
(2)
Once fully approved, I also plan to distribute it broadly within JRA1 (JRA1 Leader Telcon + mailing list) since it’s really a
valuable document.
Very well work and a key document indeed.
(3)
Given its unique nature and having several developers in the community that build on-top-of-EMI solutions (e.g. portals), we might
discuss whether the release plan could have a prominent place on our Website.
I believe many (also non EGI folks) would be interested!
Additional recommendations (not affecting the document content, e.g. recommendation for future work)
The release plan is quite long and perhaps more aspects could be referenced rather than described in detail in the document (e.g. third-level, fourth-level bullet list details)
Detailed comments on the content
Additional recommendations can be found in the uploaded document using the word 'track changes' functionality.
Note 1: The reviewers must list here any observation they want to track explicitly and that require interaction with the authors
Alternatively all changes must be listed in the document itself using Word change tracking features (if you use Word)
Note 2: These comments have to be explicitly addressed by the authors and the action taken must be clearly described
N° |
Page |
Section |
Observations and Replies |
Is Addressed? |
1 |
xx |
x.y |
Sequence of comments and replies separated by twiki signature and date |
|
|
2 |
|
|
|
|
|
3 |
|
|
|
|
|
4 |
|
|
|
|
|
Any other modification, spelling or grammatical corrections, etc must be done directly in the document using tracked changes or similar mechanisms that allows the authors to identify which correction is suggested.
--
FloridaEstrella - 10-Jan-2011