@@ -14,13 +14,13 @@ Add new agenda items under the `Your __new__() agenda items` heading
14
14
15
15
| Name | Initials | GitHub ID | Affiliation |
16
16
| ----------------------- | -------- | --------------- | --------------------------- |
17
- | | | | |
18
- | | | | |
19
- | | | | |
20
- | | | | |
21
- | | | | |
22
- | | | | |
23
- | | | | |
17
+ | Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
18
+ | Filipe Fernandes | FF | ocefpaf | conda-forge |
19
+ | Klaus Zimmermann | KZ | zklaus | Quansight |
20
+ | Bianca Henderson | BH | beeankha | Anaconda |
21
+ | Marius van Niekerk | MvN | mariusvniekerk | Voltron Data |
22
+ | Dasha Gurova | DG | dashagurova | Anaconda/conda |
23
+ | Matthew Becker | MRB | beckermr | cf |
24
24
| | | | |
25
25
| | | | |
26
26
@@ -32,15 +32,50 @@ X people total
32
32
33
33
### From previous meeting(s)
34
34
35
- - [ ]
35
+ - [X] (JK) CUDA 12 migration close out?
36
+ - https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/6263 (HV: already closed since this point was put on the agenda)
37
+ - How to handle CUDA 12.x?
38
+ - [ ] (JK) (When would we like to) close Python 3.12 migration?
39
+ - https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/5892
40
+ - [ ] (JK) NumPy 2 (check-in)
41
+ - https://github.com/conda-forge/conda-forge.github.io/issues/1997
42
+ - [ ] (JK) R 4.4 / UCRT (check-in)
43
+ - https://github.com/conda-forge/r-base-feedstock/issues/325
44
+ - Still ongoing, but not paused, very well alive
45
+ - For ` ar ` issues, use ` $AR ` (or ` binutils ` but careful with cross-compiling because). Patch as necessary.
46
+ - [ ] (JRG): Asking for feedback in this issue about CPU instructions, ` -march ` flags, etc
47
+ - [ ] https://github.com/conda-forge/conda-forge.github.io/issues/2251
36
48
37
49
### Active votes
38
50
39
51
- [ ]
40
52
41
53
### Your __ new__ () agenda items
42
54
43
- - [ ]
55
+ - [ ] 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
56
+ - [ ] 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
57
+ - [ ] Version bumping not available yet
58
+ - [ ] Migrator not yet "tested" (going to try to add a package to a osx-arm64 migration soon!)
59
+ - [ ] Experimental cache is already being tried by some multi-output packages
60
+ - [ ] https://github.com/conda-forge/cherab-inversion-feedstock/blob/9aeb59568a2099551ff5e34f433b29a1beb6ee03/recipe/recipe.yaml#L14
61
+ - [ ] Bunch of other issues / shortcomings going to be fixed asap in ` rattler-build `
62
+ - [ ] IF: When to move to recipe.yaml in complicated recipes. Would rather wait for compiled things until bugs are fixed.
63
+ - [ ] https://github.com/prefix-dev/rattler-build/issues/955
64
+ - [ ] https://github.com/prefix-dev/rattler-build/issues/952
65
+ - [ ] WV: Pixi in CI pipelines
66
+ - [ ] WV: Why mamba update on CI?
67
+ - [ ] IF: Old mamba bug, might be resolved now.
68
+ - [ ] https://github.com/conda-forge/conda-forge.github.io/issues/2323
69
+ - [ ] Marius tried locks and got shot down - see https://github.com/conda-forge/conda-forge-lockfiles
70
+ - [ ] Two separate issues:
71
+ - [ ] performance for bootstrapping: lockfiles?
72
+ - [ ] Action item: measure how long it takes. Might be different across OSs.
73
+ - [ ] local debugging with build-locally.py but with pixi
74
+ - [ ] MRB: infrachanges for rerendering / linting / version commands
75
+ - [ ] webservices now sends all jobs that process recipes (except for team updates which only read text) to GHA actions
76
+ - [ ] those GHA jobs run out of conda-forge-webservices actions instead of the actions on repos
77
+ - [ ] isolation of recipes is done using separate GHA jobs (which are separate VMs) and also docker containers
78
+ - [ ] if you see issues bump me
44
79
45
80
### Pushed to next meeting
46
81
0 commit comments