Skip to content

Commit 75f7145

Browse files
github-actions[bot]github-actions[bot]
committed
Update src/orga/minutes/2023-11-15.md
1 parent 72e0739 commit 75f7145

File tree

1 file changed

+114
-11
lines changed

1 file changed

+114
-11
lines changed

‎src/orga/minutes/2023-11-15.md

Lines changed: 114 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -13,36 +13,139 @@ Add new agenda items under the `Your __new__() agenda items` heading
1313

1414
| Name | Initials | GitHub ID | Affiliation |
1515
| ----------------------- | -------- | --------------- | --------------------------- |
16+
| Marcel Bargull | MB | mbargull | Bioconda/cf |
17+
| Bianca Henderson | BH | beeankha | Anaconda |
18+
| Mark Anderson | MAA | markan | Anaconda |
19+
| Marcelo Trevisani | MDT | marcelotrevisani | conda-forge |
20+
| Isuru Fernando | IF | isuruf | Quansight |
21+
| Wolf Vollprecht | WV | wolfv | prefix.dev |
22+
| Dave Clements | DPC | tnabtaf | Anaconda |
23+
| Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
24+
| Matthew R Becker | MRB | beckermr | cf |
25+
| John Kirkham | JK | jakirkham | NVIDIA/cf |
1626
| | | | |
1727
| | | | |
1828
| | | | |
1929
| | | | |
20-
| | | | |
21-
| | | | |
22-
| | | | |
23-
| | | | |
24-
| | | | |
25-
26-
X people total
30+
14 people total
2731

2832
### Standing items
2933

3034
- [ ]
3135

3236
### From previous meeting(s)
3337

34-
- [ ]
38+
- [x] (HV) archspec-packages, next steps (feel free to discuss in my absence)
39+
- we have [microarch-level](https://github.com/conda-forge/microarch-level-feedstock) package now :tada:
40+
- are we ready/willing to build packages for different arches?
41+
- do we want to set minimal guidelines to avoid CI explosion from feedstocks indiscriminately wanting to build v2,v3,v4 because "it's obviously faster"?
42+
- need to go through and check whether runtime dispatching is available
43+
- how to detect macroarchitecture (x86_64 for example)? This was in `__arch`, but is now not there. how should this be included?
44+
- Change existing string to include with micro architecture?
45+
- New virtual package?
46+
- Discussion continues in [issue](https://github.com/conda-forge/conda-forge.github.io/issues/1261)
47+
- [x] (JK) m2 recipes
48+
- Isuru needs time.
49+
- (IF) CDT build type thing for m2 (tools).
50+
- https://github.com/conda-forge/msys2-recipes
51+
- https://github.com/conda-forge/m2-builds
52+
- (IF) m2w64 packages would be regular feedstocks
53+
-
54+
- [x] (JK) Windows ARM
55+
- (IF) Call last week with Finn (from Microsoft)
56+
- (IF) ARM-64 windows CI set up.
57+
- (IF) Not the whole things, but progress
58+
- Use ARM64 image using an X86 installer, then use emulation
59+
- (IF) Will also need m2 recipes (as Python needs these to build)
3560

36-
### Active votes
3761

38-
- [ ]
3962

40-
### Your __new__() agenda items
63+
### Active votes
4164

4265
- [ ]
4366

67+
### Your `__new__()` agenda items
68+
69+
- [x] (HV) / (WV) Discuss `{{ stdlib("c") }}` vs. `{{ compiler("c", stlib=...) }}`, see [here](https://github.com/conda/conda-build/issues/5053).
70+
- (WV)
71+
- Still in favor of one Jinja function. Having 2 makes it messy
72+
- Can try and fix it later if there is demand.
73+
- (IF)
74+
- This would add more technical debt to conda-build (?)
75+
- (WV)
76+
- conda-build is so much technical debt already.
77+
- how much should we worry about it.
78+
- (MB)
79+
- agree with both
80+
- (IF)
81+
- One jinja function would be good, but there isn't a way to do that now.
82+
- [x] (JK) Travis CI update
83+
- Hit issues a week ago with staged recipes because Travis gave us API issues
84+
- Also long term issues with token resets from Travis.
85+
- Had us resync the bots
86+
- GitHub bots couldn' start CI...
87+
- (MB) Did anyone from conda-forge ask for linux-arm?
88+
- (JK) We haven't even discussed it.
89+
- (IF) JRG addded a feature to admin-requests.
90+
- We could stop registering all feedstocks when we add them.
91+
- Could require developers to request them.
92+
- 90% of developers don't really need this.
93+
- (JK) Could maintainers ask for Travis CI support later?
94+
- What's the prcess for that?
95+
- https://github.com/conda-forge/admin-requests/blob/main/grant_access/travis/example.txt
96+
- [x] (JK) Windows CUDA 12
97+
- Have done more testing with cupy - found small bugs which have been fixed.
98+
- Ok to migrate? Yes
99+
- Ok restarting existing migrator and adding Windows? Yes
100+
- https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5121
101+
- [x] (JK) Results from conda-smithy 3.28.0
102+
- https://github.com/conda-forge/conda-smithy/releases/tag/v3.28.0
103+
- https://github.com/conda-forge/conda-smithy/releases/tag/v3.29.0
104+
- How are things going with the new releases?
105+
- libmamba solver is now the default
106+
- Any issues
107+
- (MRB)
108+
- Seen a few issues
109+
- Don't have the latest version of Boa
110+
- (JRG)
111+
- Seen reports where solver failed to write back because of key-errors
112+
- Related to channels
113+
- PR merged today. Hopefully released this week
114+
- https://github.com/conda/conda-libmamba-solver/pull/365
115+
- (IF)
116+
- could specify miniforge version
117+
- we use miniforge in all of our CI
118+
- (JRG) Want to separate tooling issues from distribution issues
119+
- (JRG) TL;DR Bumped into a couple issues. Working those out
120+
- [x] (HV) libboost 1.82 migration update & next steps
121+
- almost 200 PRs [merged](https://github.com/pulls?q=is%3Apr+org%3Aconda-forge+archived%3Afalse+%22Rebuild+for+libboost+1.82%22+is%3Amerged+)
122+
- long tail of packages that don't build (e.g. have open PRs for old boost migrations)
123+
- ~70% are estimated to be done
124+
- do one last pass for bot errors and unsolved feedstocks, then should be close
125+
- [x] (JK) Custom license discussion
126+
- https://github.com/conda-forge/staged-recipes/pull/24449
127+
- https://github.com/conda-forge/unicorn-binance-websocket-api-feedstock
128+
- Claiming MIT when submitters actually are using a custom license
129+
- How do we cope?
130+
- We can't just eliminate custom licenses.
131+
- (MB) in this specific case we can say you can't lie about licensing.
132+
- They need to fix their metadata.
133+
- "We are feeling ucomfortable with the licensing so not comfortable reviewing it."
134+
44135
### Pushed to next meeting
45136

137+
- [ ] (JK) Miniforge 23.10
138+
- https://github.com/conda-forge/miniforge/issues/511
139+
- [ ] (JK) NumPy 2.0
140+
- https://github.com/numpy/numpy/pull/24861#issuecomment-1776781838
141+
- [ ] (JK) CUDA Docker images
142+
- [ ] (HV) what [to do](https://github.com/conda-forge/cdt-builds/issues/66) with CDTs for Alma 8
143+
- make checklist with CDTs, for checking whether we can switch each to conda packages?
144+
- [ ] (DJC) Policy for CUDA arch targets and pruning CUDA archs
145+
- https://github.com/conda-forge/conda-forge.github.io/issues/1901
146+
- Some packages are too big to build within the 6 hour CI limit while targeting many CUDA architectures
147+
- examples include libmagma, libtorch
148+
- The linked discussion is about which CUDA archs should be targeted when the upstream project does not have defaults and in what order to drop archs in order to complete builds within the 6 hours
46149
- [ ]
47150

48151
### CFEPs

0 commit comments

Comments
 (0)