---
tags: [meeting-notes]
title: '2024-10-02'
---
# conda-forge core meeting 2024-10-02

Add new agenda items under the `Your __new__() agenda items` heading

- [Zoom link](https://zoom.us/j/9138593505?pwd=SWh3dE1IK05LV01Qa0FJZ1ZpMzJLZz09)
- [What time is the meeting in my time zone](https://dateful.com/convert/utc?t=5pm)
- [Previous meetings](https://conda-forge.org/community/minutes/)

## Attendees

| Name | Initials | GitHub ID | Affiliation |
| ----------------------- | -------- | --------------- | --------------------------- |
| Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
| Filipe Fernandes | FF | ocefpaf | conda-forge |
| Klaus Zimmermann | KZ | zklaus | Quansight |
| Bianca Henderson | BH | beeankha | Anaconda |
| Marius van Niekerk | MvN | mariusvniekerk | Voltron Data |
| Dasha Gurova | DG | dashagurova | Anaconda/conda |
| Matthew Becker | MRB | beckermr | cf |
| | | | |
| | | | |

X people total

### Standing items

- [ ]

### From previous meeting(s)

- [X] (JK) CUDA 12 migration close out?
- https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/6263 (HV: already closed since this point was put on the agenda)
- How to handle CUDA 12.x?
- [ ] (JK) (When would we like to) close Python 3.12 migration?
- https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/5892
- [ ] (JK) NumPy 2 (check-in)
- https://github.com/conda-forge/conda-forge.github.io/issues/1997
- [ ] (JK) R 4.4 / UCRT (check-in)
- https://github.com/conda-forge/r-base-feedstock/issues/325
- Still ongoing, but not paused, very well alive
- For `ar` issues, use `$AR` (or `binutils` but careful with cross-compiling because). Patch as necessary.
- [ ] (JRG): Asking for feedback in this issue about CPU instructions, `-march` flags, etc
- [ ] https://github.com/conda-forge/conda-forge.github.io/issues/2251

### Active votes

- [ ]

### Your __new__() agenda items

- [ ] DG: conda build tools meetings are coming back up: next one Oct 10th. Check with Bianca. See conda community events calendar: https://conda.org/community/calendar
- [ ] WV: rattler-build rollout is going on and [seems to progress nicely](https://github.com/search?type=code&q=org%3Aconda-forge+path%3Arecipe%2Frecipe.yaml). Outstanding items
- [ ] Version bumping not available yet
- [ ] Migrator not yet "tested" (going to try to add a package to a osx-arm64 migration soon!)
- [ ] Experimental cache is already being tried by some multi-output packages
- [ ] https://github.com/conda-forge/cherab-inversion-feedstock/blob/9aeb59568a2099551ff5e34f433b29a1beb6ee03/recipe/recipe.yaml#L14
- [ ] Bunch of other issues / shortcomings going to be fixed asap in `rattler-build`
- [ ] IF: When to move to recipe.yaml in complicated recipes. Would rather wait for compiled things until bugs are fixed.
- [ ] https://github.com/prefix-dev/rattler-build/issues/955
- [ ] https://github.com/prefix-dev/rattler-build/issues/952
- [ ] WV: Pixi in CI pipelines
- [ ] WV: Why mamba update on CI?
- [ ] IF: Old mamba bug, might be resolved now.
- [ ] https://github.com/conda-forge/conda-forge.github.io/issues/2323
- [ ] Marius tried locks and got shot down - see https://github.com/conda-forge/conda-forge-lockfiles
- [ ] Two separate issues:
- [ ] performance for bootstrapping: lockfiles?
- [ ] Action item: measure how long it takes. Might be different across OSs.
- [ ] local debugging with build-locally.py but with pixi
- [ ] MRB: infrachanges for rerendering / linting / version commands
- [ ] webservices now sends all jobs that process recipes (except for team updates which only read text) to GHA actions
- [ ] those GHA jobs run out of conda-forge-webservices actions instead of the actions on repos
- [ ] isolation of recipes is done using separate GHA jobs (which are separate VMs) and also docker containers
- [ ] if you see issues bump me

### Pushed to next meeting

- [ ]

### CFEPs

- [ ]