CTA Release Roadmap Room: 513/R-068 ### Release 4.8.10-1 * Release date: 12/06 * Pre-prod deployment date: 14/06 * Prod deployment date: 15/06 * Prod catalogue update date: 23/06 * [Milestone link](https://gitlab.cern.ch/cta/CTA/-/milestones/20#tab-issues) * *Pure catalogue release 13.0* * *Fixes deployment issue: code compatible with catalogue versions <= 13.0* ### Public Release * Latest version available on public repo: **v4.8.7-1**, **v5.8.7-1**

CTA dev topics Room: 513/R-068 ### Option to remove fflush in mhvtl code * Issue link: [#283](https://gitlab.cern.ch/cta/CTA/-/issues/283#note_6859096) ### Apply unified code style / formatting * Issue link: [#98](https://gitlab.cern.ch/cta/CTA/-/issues/98) ### Rework catalogue release procedure and deployment path * Issue link: [#397](https://gitlab.cern.ch/cta/CTA/-/issues/397) ### Schema verify fails for postgres in catalogue v13 * Issue link: [#402](https://gitlab.cern.ch/cta/CTA/-/issues/402) * New package version *4.7.10-2*, or *4.8.0-1* (pivot)? ### Modifications to eos `evict`/`stagerrm` command * Issue link: [#278](https://gitlab.cern.ch/cta/CTA/-/issues/278) ### Refactor RDBMS functions for catching SQL exceptions * Issue link: [#401](https://gitlab.cern.ch/cta/CTA/-/issues/401) ### Keep cta-taped alive if at least one drive handler is alive * Issue link: [#303](https://gitlab.cern.ch/cta/CTA/-/issues/303) ### [Ops] Repacks failing because of open denied * Issue link: [#Ops-1101](https://gitlab.cern.ch/cta/operations/-/issues/1101) ### [Ops] Increase the repack expanding limit from 2 to 10 * Issue link: [#Ops-1100](https://gitlab.cern.ch/cta/operations/-/issues/1100) ### "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.