JRA1 monthly telcon

Thursday 8 Mar 2012, 10:00 → 10:30 Europe/Zurich

EVO

Information on the EMI 2 inventory as of the last develpment code freeze, and how to proceed with unfinished development.

JRA1 meeting 08.03.2012 Where: EVO Participants: Approximately 12 joined the meeting Minutes: - Now that the final code freeze date has passed, no more development will be allowed to enter the EMI 2 release. - Last week the JRA1 management and release manager had a meeting where we went through the PT tasks planned for EMI 2 release. - The goal was to make an inventory of what would be released as part of EMI 2 now that the RC3 code freeze date has passed, meaning that final decisions had to be taken on which development made it to the EMI 2 release. - The decisions were based on the available information in the development tracker. - Did not consider designs, studies and agreements as those were not affected by the code freeze - Did not consider the platform support as these will be taken in a separate meeting. Some statistics: - Total number (excluding platform support): 111 - Designs, studies and agreements were not considered for the decisions: 8 - Tasks were split into four: Tasks that made it, tasks that partly made it, tasks that almost made it and tasks that we have doubts if should continue 1) The task was finished and should be released. (tasks with planned release "EMI 2" and status "done") 79 tasks 2) The task was not finished, but was ready enough to be released as a prototype. The prototype should be released, but development will continue and finished code will be delivered in an EMI 2 update. (tasks with planned release "EMI 2 update" and should be finished 2012-07-02, corresponds to decisions (2) and (3)) 9 tasks 3) The task was not ready enough to be released, but still close to finished. The code should not be released, but development should continue and finished code will be delivered in an EMI 2 update. (tasks with planned release "EMI 2 update" and should be finished 2012-07-02, corresponds to decisions (2) and (3)) 8 tasks 4) The task was not ready for release and it is unclear if development should continue. The task is put on hold and PTB should decide whether the development should continue or not. (tasks with planned release "PTB to decide") - Notes on tasks with "PTB to decide": - It's well known that there are too many development tasks in this project - PTB has been given the mandate to cut development tasks - The tasks with planned release "PTB to decide" were roughly chosen from tasks with 50% or less completeness and where the remaining work needed is very unclear 7 tasks How to progress with unfinished tasks: - Tasks were an alpha/prototype is allowed to be release should - clearly specify in the release notes that the feature/product is unfinished - document what is not finished - Further development should continue, but: - You cannot release the further development before EMI 2 update 1 (beginning of July) - If the feature/product was not allowed for EMI 2 you cannot market it as part of EMI 2 (even if you for accidentally or for any other reason shipped the code with, e.g., the RC4 build) - Unfinished studies/designs/agreements - Reports must be ready by 15 April (design freeze deadline)