CTA Release Workflow Room: 31/S-028 * [Release procedure instructions](https://eoscta.docs.cern.ch/cta/tag_cta/)

CTA Release Roadmap Room: 31/S-028 See [CTA Release Roadmap](https://gitlab.cern.ch/cta/CTA/-/wikis/CTA-Release-Roadmap) ## Release 4.8.0-1 * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/4#tab-issues) * Release date: 28 Nov * Pre-prod deployment date: 30 Nov * Prod deployment date: 5 Dec ## Release 4.8.1-1 - DELAYED (see minutes) * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/10#tab-issues) * Release date: TBD (already stress tested) * Pre-prod deployment date: TBD * Prod deployment date: TBD * *Both 4.8.1-1 and 4.8.2-1 will be released simultaneously* ## Release 4.8.2-1 - DELAYED (see minutes) * [Milestones link](https://gitlab.cern.ch/cta/CTA/-/milestones/11#tab-issues) * Release date: TBD * Pre-prod deployment date: TBD * Prod deployment date: TBD * *Catalogue v13 release* * *Both 4.8.1-1 and 4.8.2-1 will be released simultaneously* ## Public Release * Version available on public repo: **v4.7.14-1**, **v5.7.14-1** * New versions will be released after we have used it internally in production.

CTA dev topics Room: 31/S-028 ### Review scheduler retry logic for archive and retrieve * The retry logic should take into account the type of the error found, in order to decide if and how long the queue should sleep between retries. * For details check [#37](https://gitlab.cern.ch/cta/CTA/-/issues/37) ### Handle 'unavailable' files in user and repack retrieves originated from problematic tapes * When to check for unavailable files, during the retrieve workflow? * For details check [#218](https://gitlab.cern.ch/cta/CTA/-/issues/218) ### 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 version v4.8.0-1 on production. ### 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) ### r_alice_test_datachallenge archives queues not being absorbed * For details check ops issue [#ops-918](https://gitlab.cern.ch/cta/operations/-/issues/918) ### "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: 31/S-028 ### 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: 31/S-028 ### Other * Room 513/R-068 is booked every week, until the EOY, for the CTA dev meeting.