Skip to content

Commit ae30c7b

Browse files
Update src/orga/minutes/2023-10-04.md
1 parent 99b92c7 commit ae30c7b

File tree

1 file changed

+51
-13
lines changed

1 file changed

+51
-13
lines changed

src/orga/minutes/2023-10-04.md

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

1414
| Name | Initials | GitHub ID | Affiliation |
1515
| ----------------------- | -------- | --------------- | --------------------------- |
16+
| Dave Clements | DPC | tnabtaf | Anaconda |
17+
| Daniel Ching | DJC | carterbox | Argonne National Laboratory |
18+
| Marcel Bargull | MB | mbargull | Bioconda/cf |
19+
| John Kirkham | JK | jakirkham | NVIDIA/cf |
20+
| Eric Dill | ED | ericdill | Anaconda/cf |
21+
| Filipe Fernandes | FF | ocefpaf | conda-forge |
22+
| Carl Anderson | CPA | barabo | Anaconda |
1623
| | | | |
17-
| | | | |
18-
| | | | |
19-
| | | | |
20-
| | | | |
21-
| | | | |
22-
| | | | |
23-
| | | | |
24-
| | | | |
24+
| Matt Becker | MRB | beckermr | cf |
2525

26-
X people total
26+
15 people total
2727

2828
### Standing items
2929

3030
- [ ]
3131

3232
### From previous meeting(s)
3333

34-
- [ ]
34+
- [x] (JK) NumPy 2.0 planning
35+
- https://github.com/conda-forge/conda-forge.github.io/issues/1997
36+
- https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/issues/516
37+
- HV: Should be possible to only build against 2.x, result [will be](https://githubx.com/conda-forge/conda-forge-pinning-feedstock/issues/4816#issuecomment-1717038980) ABI-compatible with 1.2x
38+
- IF: It will **not** be ABI compatible if the package author changes
39+
`NPY_TARGET_VERSION` macro. Need ways to ensure that it does not happen.
40+
- NumPy 2 coming out early next year.
41+
- What's our timeline?
42+
- JK: Ask the NumPy devs to embed the NPY_TARGET_VERSION in the resulting binaries as a string?
43+
- Will continue further discussion.
44+
45+
- [x] (JL) FYI the creation of a conda "build tools" team under conda governancy policy (still federated until team figures out team charter) for conda-build and hopefully other build tools, welcome to join:
46+
- [ ] https://github.com/conda/conda-build/issues/4698
3547

3648
### Active votes
3749

3850
- [ ]
3951

40-
### Your __new__() agenda items
41-
42-
- [ ]
52+
### Your `__new__()` agenda items
53+
54+
55+
- [x] (HV) Drop PyPy on aarch/ppc?
56+
- PyPy support is already stretched very thin, to the point that we considered dropping it (c.f. [here](https://github.com/conda-forge/pypy3.6-feedstock/issues/104)), haven't done a pypy3.10 migration yet, various high impact bugs remain, etc.
57+
- We have no CI on the [feedstock](https://github.com/conda-forge/pypy3.6-feedstock) for aarch/ppc (cannot cross-compile, travis times out), and manual builds put extra strain on maintenance, and sometimes just don't happen (e.g. missing 7.3.12 & 7.3.13, the last two versions), meaning missed bugfixes etc.
58+
- Rather than risk PyPy support overall by overwhelming the PyPy devs (or demanding that someone from core do manual builds for every PR), I suggest to drop PyPy on aarch/ppc; usage numbers for those builds are on the order of 1 in 10'000 users. This is not great, but IMO more sensible vis-à-vis the very constrained PyPy-resources.
59+
- Isuru does these builds. This is not causing larger problems in CF, therefore, it's up to maintainers (Isuru) to make this decision?
60+
- Axel: But it has been a problem for some downstream packages.
61+
- Axel: will report problems as they arise.
62+
- AI: If we want to drop PyPy ARM/PPC, raise an issue on the webpage repo or pinning repo to discuss
63+
- [x] (HV) Compiler bump: GCC 13 & Clang 16
64+
- [PR](https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4890) is ready, relevant info in the OP.
65+
- Isuru: Clang 16 now, GCC 13 in a bit.
66+
- [x] (JRG) Intention to submit a CZI EOSS6 letter of intent with Wolf.
67+
- Rough draft: https://hackmd.io/m_dJizu9TWGRI8RprLO-Yg
68+
- Theme: the future of conda-build, transitioning to new tooling (`boa`, `rattler-build`) and improved build reproducibility in conda-forge.
69+
- Interested in knowing if this is a terrible idea.
70+
- Deadline: Oct 16th.
71+
- [x] (JRG) GPU CI status:
72+
- Passing CI for x64 `cupy` at https://github.com/conda-forge/cf-autotick-bot-test-package-feedstock/pull/466 with [global cirun config](https://github.com/conda-forge/.cirun) (simpler conda-smithy changes)
73+
- [`admin-requests` PR](https://github.com/conda-forge/conda-smithy/pull/1703) ready. Jaime to review / debug in the coming days.
74+
75+
- [x] (IF) m2-recipes https://github.com/conda-forge/staged-recipes/pull/24112
76+
- [x] (WV) Sovereign Tech Fund contract
77+
- [ ] libsolv - Rust port
78+
- [ ] rattler-build conda-forge integration
79+
- [ ] conda-forge reproducibility evaluation
80+
- [x] (WV) Please don't forget to vote for conda steering council :)
4381

4482
### Pushed to next meeting
4583

0 commit comments

Comments
 (0)