CTA Release Roadmap Room: 513/R-068 ### Release 4.8.8-0.rc1/cr2/rc3 * Release date: 19 May, 19 May, 24 May * Pre-prod deployment date: 19 May, 19 May, 24 May * Prod deployment date: --- * Testing new encryption logic ### Release 4.8.8-1 * Release date: TDB * Pre-prod deployment date: TBD * Prod deployment date: TBD * [Milestone link](https://gitlab.cern.ch/cta/CTA/-/milestones/19#tab-issues) * *Based on the latest commit from main* * *Include new encryption logic developed by Vova* ### Release 4.8.9-1 * Release date: TBD * Pre-prod deployment date: TBD * Prod deployment date: TBD * [Milestone link](https://gitlab.cern.ch/cta/CTA/-/milestones/20#tab-issues) * *Pure catalogue release 13.0* * *Requires changes to catalogue schema to be all merged* ### Public Release * Latest version available on public repo: **v4.8.7-1**, **v5.8.7-1**

CTA dev topics Room: 513/R-068 ### Catalogue 13.0 release * Do after next code release (will be release 4.8.9-1). * Are all changes ready? [link for merge_requests](https://gitlab.cern.ch/cta/cta-catalogue-schema/-/merge_requests) ### EOS-5 Moving all our deployment and dev work to EOS-5 is needed. Usage of EOS-4 should be avoided across our entire dev and deployment stack. Important topics for EOS-5: * Deployment to production * Buildup tree scrips (dev setup) * Using EOS-5 on CI with HTTPS (requires certificates) * Removing support for EOS-4 (change `stagerrm` to `evict`?) ### Future changes in CTA dev team * Lasse and Vova are leaving soon :( Many thanks!! * Dev team will need reinforcements (Pablo, Richard?) Review last tasks. Discuss handover strategy. Some possible tasks for the "newcomers": * Keep cta-taped alive if at least one drive handler is alive [#303](https://gitlab.cern.ch/cta/CTA/-/issues/303) * Migration of CTA system tests (and other scripts) from Bash to Python. ### "Needs discussion" topics * [Issues link](https://gitlab.cern.ch/cta/CTA/-/issues?sort=updated_desc&state=opened&label_name[]=Needs+Discussion) ### "Dev issue needed" topics * [Ops issues link](https://gitlab.cern.ch/cta/operations/-/issues/?label_name=Dev%20issue%20needed)

dCache Integration Room: 513/R-068 ### AOBs

AOB Room: 513/R-068 ###AOBs

CTA dev board review Room: 513/R-068 ### Objective * Look at the active issues in our CTA dev board. * Decide if they should be kept, removed, reassigned, prioritised, etc. ### Review "Blocked" labeled issues * Full CTA board: [link](https://gitlab.cern.ch/cta/CTA/-/boards/19473)