EMI 1 RC0 Milestone The RC0 milestone was achieved on 22nd of February. This milestones represented the first complete integration of all EMI 1 components in a single build and had a planned success rate threshold of 90%. The final build reached 91%. The build logs are available on the EMI 1 roadmap page at
New ETICS client series 1.5.x New releases of the ETICS Clients are being produced during these weeks. The new 1.5 series introduces functionality needed to integrate mock within the standard ETICS build process and resolve dependencies directly from the locally configured Yum repositories. It also fixes a number of long standing bugs. More details at <br/ http://etics.cern.ch/eticsPortal/
QA Policies The EMI QA Policies keep being revised to verify they are ready for the final two months of certification of the EMI 1 release. In particular two very important policy revisions regulating the EMI 1 preparation have been approved by the ECB
Furthermore, the EMI Component Release Check List and the accompanying report templates are available to assist the release preparation and certification
The TD and the Release Manager have gone through all the component release entries for EMI 1 in the release tracker (https://savannah.cern.ch/task/?group=emi-releases) and made a substantial consolidation. During the consolidation, a number of changes and updates were made to every tracker entry. As a result, the component entries of the tracker reflect a more reasonable granularity of EMI 1 software components. After these changes the component release entries are ready for the PTs to take over and start providing the required information including release note, RfC list, package lists, test and certification reports.
QA and Certification Training A three-part internal training events is taking place from 24 Feb to 3 March. It is dedicated to explaining the SA2 build and test tools and certification procedures. The sessions agenda is available at
Update to deliverables guidelines An update to the deliverable guidelines has been defined. This update provides instructions to handle update deliverables, that is all the deliverables who are follow-up versions of already released deliverables, like the technical plans for the second year or a new instance of the dissemination plan, etc. Please note that this doesn't concern updates to existing deliverables (for example to fix typos or correct statements) for which the existing amendment procedure applies. The update is available at