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.8.2-1 * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/13#tab-issues) * Release date: 14 Dec * Pre-prod deployment date: 16 Dec * Prod deployment date: 19 Dec * *Optimisations on catalogue DB queries* ## Public Release * Latest version available on public repo: **v4.7.14-1**, **v5.7.14-1**

CTA dev topics Room: 513/R-068 ### Tape server querying DB at very high rate * For details check [#155](https://gitlab.cern.ch/cta/CTA/-/issues/155) ### Tapes get stuck on PENDING states if there is no queue object * The causes for this bug have been determined. We need to discuss the proposed solutions. * For details check [#258](https://gitlab.cern.ch/cta/CTA/-/issues/258) ### Improvements on CTA catalogue schema git workflow * CTA catalogue schema releases/development are not tracked/secured in the same way as main. Here are two possible solutions for discussion: * Use a new special branch: [#263](https://gitlab.cern.ch/cta/CTA/-/issues/263) * Use a git submodule: [#254](https://gitlab.cern.ch/cta/CTA/-/issues/254) ### Allow VO override for repack * For details check [#31](https://gitlab.cern.ch/cta/CTA/-/issues/31) ### CTA cannot archive files on MHVTL ULTRIUM config * CTA CI and buildtree scripts have hardcoded depencies on the MHVTL STK configuration. This means that we cannot use the new MHVTL configuration with ULTRIUM libraries without substancial development work... * [257](https://gitlab.cern.ch/cta/CTA/-/issues/257), [146](https://gitlab.cern.ch/cta/CTA/-/merge_requests/146#note_6325496), [177](https://gitlab.cern.ch/cta/CTA/-/issues/177) ### Add new purchase order field to the tape table * For details check [#Ops-964](https://gitlab.cern.ch/cta/operations/-/issues/964) ### cta-taped not dismounting tapes on uncaught exception * For details check [#Ops-961](https://gitlab.cern.ch/cta/operations/-/issues/961) ### stagerrm issues continued * For details check [#Ops-865](https://gitlab.cern.ch/cta/operations/-/issues/865) ### "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)

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 unlabelled issues * Unlabelled issues list: [link](https://gitlab.cern.ch/cta/CTA/-/issues/?sort=updated_desc&state=opened&not%5Blabel_name%5D%5B%5D=workflow%3A%3AAccepted&not%5Blabel_name%5D%5B%5D=workflow%3A%3AAssigned&not%5Blabel_name%5D%5B%5D=workflow%3A%3AIn%20Progress&not%5Blabel_name%5D%5B%5D=workflow%3A%3ABlocked&not%5Blabel_name%5D%5B%5D=workflow%3A%3ADone&not%5Blabel_name%5D%5B%5D=Release&first_page_size=100) ### Review "In progress" issues * Full CTA board: [link](https://gitlab.cern.ch/cta/CTA/-/boards/19473) ### Review specific topic * Every week we review the issues of one topic. * This week: [*"Scheduler"*](https://gitlab.cern.ch/cta/CTA/-/boards/19473?label_name[]=Scheduler) and [*"Object Store"*](https://gitlab.cern.ch/cta/CTA/-/boards/19473?label_name[]=Scheduler&label_name[]=Object%20Store) labels

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