CTA Release Workflow Room: 513/R-068 * [Release procedure instructions](https://eoscta.docs.cern.ch/cta/tag_cta/)

CTA Release Roadmap Room: 513/R-068 See [CTA Release Roadmap](https://gitlab.cern.ch/cta/CTA/-/wikis/CTA-Release-Roadmap) ## Release 4.7.6-1 * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/24#tab-issues) * Release date: 24/06/2022 * Pre-prod deployment date: 24/06/2022 * Prod deployment date: 30/06/2022 ## Release 4.7.7-1 [Catalogue v11] * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/20#tab-issues) * Release date: 1 July * Pre-prod deployment date: 4 July * Prod deployment date: 6-8 July * ***Important:** Avoid deployment on 4-5 July - High visibility event: Higgs 10th anniversary* ## Release 4.7.8-1 * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/25#tab-issues) * Release date: TBD * Pre-prod deployment date: TBD * Prod deployment date: TBD * *Will add support for multiple tape label formats* ## Future releases (4.7.x) * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/21#tab-issues) ## Public Release * [Remaining tasks](https://gitlab.cern.ch/cta/CTA/-/issues?scope=all&state=opened&label_name[]=Public%20Release)

Collaborations Room: 513/R-068 ### CTA read support for non-native tape formats (OSM/dCache and Enstore) * Project roadmap: [#1239](https://gitlab.cern.ch/cta/CTA/-/issues/1239) Add support to CTA for multiple tape label formats. * [Jorge - CTA team]: Refactor tape backend code, to allow new label formats to be implemented ([#1257](https://gitlab.cern.ch/cta/CTA/-/issues/1257), [#1263](https://gitlab.cern.ch/cta/CTA/-/issues/1263), ...). Will be released on v4.7.8, to ensure there are no regressions. ### cta-frontend-grpc integration for CTA * Project roadmap: [#1236](https://gitlab.cern.ch/cta/CTA/-/issues/1236) Integrate cta-frontend-grpc into CTA repo and RPMs * [Michael - CTA team]: CTA Frontend protobuf changes to support dCache ([#1240](https://gitlab.cern.ch/cta/CTA/-/issues/1240), [#1244](https://gitlab.cern.ch/cta/CTA/-/issues/1244)) * [Jacek - dCache]: Experimenting with streaming with gRPC (required for CTA admin client).

HTTP REST API, Activities and Priorities Room: 513/R-068 * **Priority:** Write document, with all specifications clearly defined, to be signed off by the experiments. * Topics requiring discussion: 1) How will metadata be passed using HTTP REST API (the mechanism we use for XRootD will not work). 2) What is the scope of what is meant by "Activities"? Is it for smart writing? Or for setting priorities? What is an "activity share" and what it is for? 3) How will priorities be set in HTTP REST API? Using Activities? Or using the HTTP priorities mechanism?

CTA dev topics Room: 513/R-068 ### [IMPORTANT] Hole in recycle bin logic * Data loss incident due to operator error ([#Ops-800](https://gitlab.cern.ch/cta/operations/-/issues/800)). * Unable to recall all files due to hole in our recycle bin logic ([#Ops-660](https://gitlab.cern.ch/cta/operations/-/issues/660)). ### Tape drive states * [Vova]: Project status overview. * Related issue in release v4.7.6-1: [#Ops-801](https://gitlab.cern.ch/cta/operations/-/issues/801) ### PostgreSQL scheduler DB * [David]: Project status overview. * [Jorge]: Support David setting up the CI testing stages. ### REPACKING tape state and queue cleanup * [Joao]: Project status overview. ### Move subdirectories from CTA dev repo into new repos * [Richard]: Project status overview. * [All]: Feedback about the workflow proposed by Richard by the end of next week. Decide the next steps (check [#1182](https://gitlab.cern.ch/cta/CTA/-/issues/1182)) * [Fons/All]: SonarCloud usage for static code analysis - feedback. ### Retrieve queue youngest date error * [Vlado]: Issue [#Ops-796](https://gitlab.cern.ch/cta/operations/-/issues/796) ### Other "needs discussion" topics * [Issues link](https://gitlab.cern.ch/cta/CTA/-/issues?sort=updated_desc&state=opened&label_name[]=Needs+Discussion)

AOB Room: 513/R-068 ### Meeting Rooms * Room 513/R-068 is booked every week, until the EOY, for the CTA dev meeting.