Release Management Report

Size: px

Start display at page:

Download "Release Management Report"

Isabel Dennis
8 years ago
Views:

1 ALMA Integrated Compu2ng Team Coordina2on & Planning Mee2ng #4 San2ago, November 2014 Release Management Report Ruben Soto ICT Release Manager

2 Releases (since June 2014)

3 4 incremental releases have been delivered for validacon. Ø 2 online releases: , Ø 3 offline releases: , and offline acceptances Ø CYCLE2- OFF Releases (since June 2014) Ø CYCLE2- OFF (in progress..) should be delivered at end of January (Offline ) and February (Online) 2015 for validacon.

4 2 offline acceptances Ø 201406- CYCLE2- OFF Releases (since June 2014) Ø 201411-

4 Releases (2015) 8 Incremental releases scheduled (tentacvely) for next year Ø hwps://ictwiki.alma.cl/twiki/bin/view/irm/ ReleasesPlanning#ALMA_2015_X_cycle_3_submission 3 (or 4) offline acceptances scheduled Ø March, July, September, (November) Ø should be accepted as offline SW for proposal submission cycle CYCLE3- OFF- B

cl/twiki/bin/view/irm/ ReleasesPlanning#ALMA_2015_X_cycle_3_submission 3 (or 4)

5 Releases (2015) 2 online acceptances Ø 10.6 should be accepted in January for ES operacons (in March) CYCLE2- ON- B should be created in December or early January. Ø online SW for cycle- 3 observacons. Two TRR are planned for this acceptance ( CYCLE3- ON- B): First part end of April Second part August More details at AM presentacon and acceptance calendar Ø hwps://wikis.alma.cl/bin/view/dso/acceptancecalendar

or early January. Ø 2014.6 online SW for cycle- 3 observacons.

6 SoKware Requests 43 new requests received since June 2014 Ø 37 Soeware Patch Requests 3 rejected 4 under discussion 30 approved. Ø 3 Persistent Data Structure Change 3 approved Ø 3 Release Change Request 2 approved, 1 under discussion. For small changes in the applicacons, please use Service Release as described at soeware delivery process document.

Ø 3 Persistent Data Structure Change 3 approved Ø 3 Release Change Request 2 approved,

7 Release Management Topics Late features introduced during Phase A. Ø Release contents should be defined (at least) 2 weeks before start Phase A. Aeer that date, no new features/improvements should be added to the release. Special cases should be negocated with AM, RM and TM. Ø had more than 15 features added during Phase A. VerificaCon plan and resources had to be adjusted several Cmes. Ø : No features were added aeer 2 weeks before Phase A deadline. 2 special cases were managed (ICT and ICT- 3788) were requested and both approved Ø Thanks!!

Aeer that date, no new features/improvements should be added to the release. Special cases should be negocated with AM, RM and TM. Ø 2014.

8 Release Management Topics PIPELINE Infrastructure Acceptance Ø CYCLE2- PIPELINE- B branch created from R10.4 and TRUNK. This build is compiling OK but not formally accepted. Is this Soeware currently deployed on PIPELINE cluster?? Ø PREQ- 224 was submiwed for fixing a DataPacker issue (under CYCLE2- OFF- B) Patch implemented but not fully tested. There is scll a problem with DataPacker? Ø Is there any issue to proceed with PIPELINE acceptance? Ø Should PIPELINE be scheduled as part of CYCLE3- OFF acceptance?

? Ø PREQ- 224 was submiwed for fixing a DataPacker issue (under 201403- CYCLE2- OFF- B) Patch implemented but not fully tested.

9 Release Management Topics PIPELINE HeurisCc Acceptance Ø During last management meecng was decided to accept the PIPELINE heuriscc version used at ALMA cluster. Ø Acceptance tests should be carried out for acceptance team and recommended to DMG. Ø If DMG agree, this version should be deployed at all ALMA cluster. Ø HeurisCc version used by ALMA should be specified at ALMA Science Portal. Ø More details at PIPELINE presentacon.

Ø Acceptance tests should be carried out for acceptance team and recommended to DMG.

10 Release Management Topics Deployment at ARCs Ø Deployment Manager role introduced with CYCLE2- OFF acceptance with good results. Ø SCll problems with environment standardizacon and installacon procedures. Ø Standard TesCng environment would be an assets to facilitate validacon and deployment. DB tescng account Standard offline tescng environment Resources?

Ø SCll problems with environment standardizacon and installacon procedures.

11 Release Management Topics Python Upgrade v2.7.x (Change Requests) Ø There is any objeccon to proceed? Ø Planned for ACS release ReporCng System Ø Dynamic applicacon development and deployment. Ø Details to be discussed at Maurizio s presentacon. Ø Can be extended for other applicacons (such as Archive ones) but following same principles: Isolated system (Observatory operacons not in risk in case of failure). Supported by developers. Database updates will follow SCCB workflow.