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.1-1 * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/12#tab-issues) * Release date: 12 Dec * Pre-prod deployment date: 12 Dec * Prod deployment date: 12 Dec * *Fixed protobuf error introduced by the previous release v4.8.0-1/v5.8.0-1.* ## 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: 15 Dec * Prod deployment date: - * *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 ### Review scheduler retry logic for archive and retrieve * We decided to apply a "pause" between all retries. To be discussed how this delay shall be performed. * For details check [#37](https://gitlab.cern.ch/cta/CTA/-/issues/37) ### Handle 'unavailable' files in user and repack retrieves originated from problematic tapes * How to handle unavailable files, during the repack retrieve workflow? * Use **is_unavailable** flag vs reducing **repack retrieve retries to zero**. * For details check [#218](https://gitlab.cern.ch/cta/CTA/-/issues/218) ### Amend code convention: include headers should use the complete path from the project root * Use full path vs relative file locations in header files. * For details check [#249](https://gitlab.cern.ch/cta/CTA/-/issues/249) ### Allow VO override for repack * For details check [#31](https://gitlab.cern.ch/cta/CTA/-/issues/31) ### REPACKING tape state and queue cleanup * Feedback of deploying v4.8.1-1 fix on production (fixed protobuf error - [#ops-937](https://gitlab.cern.ch/cta/operations/-/issues/937)). ### Several Free drive STALE because of long global scheduler lock aquisition time * For details check ops issue [#ops-929](https://gitlab.cern.ch/cta/operations/-/issues/929) ### stagerrm issues continued * For details check ops issue [#ops-943](https://gitlab.cern.ch/cta/operations/-/issues/943) * There are several other ***stagerrm*** issues ongoing, such as [#152](https://gitlab.cern.ch/cta/CTA/-/issues/152), [#151](https://gitlab.cern.ch/cta/CTA/-/issues/151). We should have an unified approach. ### 221213 Database intervention * For details check ops issue [#ops-948](https://gitlab.cern.ch/cta/operations/-/issues/948) ### journalctl filling disk causing problems in CI * For details check ops issue [#ops-956](https://gitlab.cern.ch/cta/operations/-/issues/956) ### "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 "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.