Skip to content

Commit f789129

Browse files
mikemhenrymikemhenry
authored
Merge branch 'main' into feat/add_mkswap_switch
2 parents fac4400 + d783c10 commit f789129

File tree

3 files changed

+185
-0
lines changed

3 files changed

+185
-0
lines changed

‎src/orga/minutes/2023-07-26.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
tags: [meeting-notes]
3+
---
4+
# conda-forge core meeting 2023-07-26
5+
6+
Add new agenda items under the `Your __new__() agenda items` heading
7+
8+
- [Zoom link](https://zoom.us/j/9138593505?pwd=SWh3dE1IK05LV01Qa0FJZ1ZpMzJLZz09)
9+
- [What time is the meeting in my time zone](https://dateful.com/convert/utc?t=5pm)
10+
- [Last week's meeting](https://hackmd.io/#REPLACE_ME#)
11+
12+
## Attendees
13+
14+
| Name | Initials | GitHub ID | Affiliation |
15+
| ----------------------- | -------- | --------------- | --------------------------- |
16+
| Dave Clements | DPC | tnabtaf | Anaconda |
17+
| Katherine Kinnaman | KK | kathatherine | Anaconda |
18+
| Bianca Henderson | BH | beeankha | Anaconda |
19+
| Keith Kraus | KJK | kkraus14 | Voltron Data |
20+
| Marcel Bargull | MB | mbargull | Bioconda/cf |
21+
| Wolf Vollprecht | WV | wolfv | prefix.dev |
22+
| Jannis Leidel | JL | jezdez | Anaconda/cf |
23+
| Matthew R Becker | MRB | beckermr | cf |
24+
| Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
25+
| John Kirkham | JK | jakirkham | NVIDIA/cf |
26+
27+
12 people total
28+
29+
### Standing items
30+
31+
- [ ]
32+
33+
### From previous meeting(s)
34+
35+
- [ ]
36+
37+
### Active votes
38+
39+
- [ ]
40+
41+
### Your `__new__()` agenda items
42+
43+
- [x] (JK) GLIBC 2.28
44+
- Red Hat source is no longer available, causing pain.
45+
- KJK Alma Linux put out announcement about being ABI compatible.
46+
- MRB: we don't yet know how this is going to shake out. Might be prudent to wait and see who wins.
47+
- How concerned are we with bug-for-bug compatibility
48+
- Some concern, but not enough to hold this back?
49+
- CUDA 12 blocked until this is resolved.
50+
- JK will create an issue
51+
- [x] (MRB) yank conda 23.7 `--json` flag is broken
52+
- This can't be! (Or, it should not have made it through testing)
53+
- https://github.com/conda/conda/issues/12928
54+
- [x] (JK) Windows ARM
55+
- CLA holdup: https://github.com/conda/conda-build/pull/4867
56+
- JL: working towards having CLA conform with governance. Working with NumFOCUS. It's coming!
57+
- Planning to patch feedstock with this change
58+
- [x] (BH) Feedstock updates for [conda](https://github.com/conda-forge/conda-feedstock/pull/213)/[conda-build](https://github.com/conda-forge/conda-build-feedstock/pull/204) July releases have been filed
59+
- [x] (DPC) [PackagingCon](https://packaging-con.org/) submission deadline is July 31.
60+
- Anyone want to submit something about conda-forge?
61+
- Jaime will submit somthing about conda. Conda-store also coming.
62+
- [x] (DPC) conda-forge presence at NumFOCUS projects meetup in Amsterdam?
63+
- Meeting is 11-13 September, just after DISC, and just before PyData Amsterdam.
64+
- Opening event the night of 10 Sept.
65+
- Collaborative work on 13 Sept
66+
- Most expenses are paid by NumFOCUS.
67+
- Wolf and Jaime will represent conda-forge.
68+
- Jannis is going for conda., but is willing to step aside.
69+
- [x] (WV) sneak peek of pixi
70+
- Pixi fresh look at tooling
71+
- Written in rust on top of rattler.
72+
-
73+
- [ ]
74+
- [ ]
75+
76+
77+
### Pushed to next meeting
78+
79+
- [ ]
80+
81+
### CFEPs
82+
83+
- [ ]

‎src/orga/minutes/2023-08-09.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
tags: [meeting-notes]
3+
---
4+
# conda-forge core meeting 2023-08-09
5+
6+
Add new agenda items under the `Your __new__() agenda items` heading
7+
8+
- [Zoom link](https://zoom.us/j/9138593505?pwd=SWh3dE1IK05LV01Qa0FJZ1ZpMzJLZz09)
9+
- [What time is the meeting in my time zone](https://dateful.com/convert/utc?t=5pm)
10+
- [Last week's meeting](https://hackmd.io/#REPLACE_ME#)
11+
12+
## Attendees
13+
14+
| Name | Initials | GitHub ID | Affiliation |
15+
| ----------------------- | -------- | --------------- | --------------------------- |
16+
| Matthew R Becker | MRB | beckermr | cf |
17+
| Katherine Kinnaman | KK | kathatherine | Anaconda |
18+
| Chris Ostrouchov | CO | costrouc | Quansight |
19+
| Cheng H. Lee | CHL | chenghlee | Anaconda/cf |
20+
| John Kirkham | JK | jakirkham | NVIDIA/cf |
21+
| | | | |
22+
| | | | |
23+
| | | | |
24+
| | | | |
25+
26+
X people total
27+
28+
### Standing items
29+
30+
- [ ]
31+
32+
### From previous meeting(s)
33+
34+
- [ ]
35+
36+
### Active votes
37+
38+
- [ ]
39+
40+
### Your __new__() agenda items
41+
42+
- [x] (JK) GLIBC 2.28
43+
- ARM / Power
44+
- NVIDA CUDA static libraries (namely cudart) using 2.17 symbols only (others like cudadevrt or culibos use none?)
45+
- (MRB) Should we mark existing glibc 2.28 sysroots as broken? Will submit PR and see what happens.
46+
- SUSE as an option potentially? Will wait and see; still unclear where everything stands
47+
- [x] (JK) Adding `conda-libmamba-solver` to Miniforge
48+
- https://github.com/conda-forge/miniforge/issues/284
49+
- Jaime (absent): I won't be able to attend today but I am very interested in solving the question above. Miniconda already ships conda-libmamba-solver, and by the September release it will be the default solver (i.e. a `conda` dependency). So it will end up in Miniforge at some point when we update to 23.9 or above. The question is: shall we ...
50+
- a) ship `mamba` in Miniforge too
51+
- a2) the above, and deprecate Mambaforge
52+
- and add links that redirect "mambaforge" -> "miniforge"
53+
- use copies to ensure old installs work (if no redirect option)
54+
- b) let `mamba` in Mambaforge only, and keep both installers separate, with the only difference being the presence of the `mamba` Python package (but note that libmamba and libmambapy are there)
55+
- Discussion: generally have miniconda/miniforge (include conda-libmamba-solver)
56+
- Are we dumping the pypy installers? keep (Up to Matti and others to decide)
57+
- Handling PyPy as separate item (so keeping PyPy installers for now)
58+
- List of artifacts
59+
- https://github.com/conda-forge/miniforge/releases/tag/23.1.0-4
60+
- Consensus is a2
61+
- [x] (JK) TexLive?
62+
- https://github.com/conda-forge/texlive-core-feedstock/issues/84
63+
- We'll need to discover and solve dependency issues before we deprecate (if we choose to do so).
64+
- We don't want to maintain a full (La)TeX distribution. Maybe add a caveat that this is for small bits of TeX, not a "full" distribution. (Reset expectations)
65+
- Plan to add README (maybe also `description` in `meta.yaml`) to reset expectations about this package
66+
- Point out release and migrator merged recently
67+
- [x] (JRG) `osx-arm64` native runners. Possibility to ask for sponsorship to MacStadium ([they do it for Homebrew](https://www.macstadium.com/customers/homebrew)) or Scaleway ([they have an OSS program](https://www.scaleway.com/en/about-us/open-source-program/)).
68+
- JRG: Sorry I will be absent but this was discussed briefly in the core chat and in case anyone missed it, posting it here for visibility.
69+
- JRG: Scaleway offers "up to" 2400€/year for OSS projects. M1 runners cost 0.11€/h, so we can afford around 2.5 runners.
70+
- Asked Amit about cirun support for scaleway
71+
- [x] (MRB) Cirrus CI
72+
- Limited free usage due to cryptominers
73+
- Cost is rather high and may involve self-hosting (ToS)
74+
- Running out of credits would mean it would stop suddenly (bad UX story)
75+
- Will look at other options
76+
77+
### Pushed to next meeting
78+
79+
- [ ] (JK) Windows ARM
80+
- [ ] (CHL) How long should we keep `osx-64` support?
81+
82+
### CFEPs
83+
84+
- [ ]

‎src/user/announcements.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,24 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
88
2023
99
----
1010

11+
2023-08-24: Bumping Minimum MacOS version to 10.13
12+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
13+
14+
We will bump the minimum MacOS version from 10.9 (released in Oct. 2013, end-of-life since
15+
Dec. 2016) to 10.13 (released Sept. 2017, end-of-life since Dec. 2020). The main reason we
16+
managed to support 10.9 this long at all, is that conda-forge is able to ship an up-to-date
17+
C++ standard library for OSX, ``libcxx``, superseding the old one present in the MacOS SDK
18+
on the system (at least from the point-of-view of the respective conda environments).
19+
20+
However, several core packages in the ecosystem now require at least 10.13 (or will very soon),
21+
in a way that we cannot be circumvent. These packages include ``libcxx``,
22+
`starting <https://discourse.llvm.org/t/libc-bumping-minimal-deployment-target-for-building-the-dylib-static-library-on-macos/68912>`_
23+
with version 17.0.
24+
This change will not affect already published artifacts, but in the near future, all new builds
25+
for OSX will require at least 10.13. This constraint will be implemented through the ``__osx``
26+
virtual package, but the details of how we will achieve this are still being worked out. Only ``conda`` versions 4.8.0 or newer have this virtual package. If you are using a system with MacOS older than 10.13 and are using ``conda`` older than 4.8.0, you will need to either upgrade ``conda`` to at least 4.8.0 or upgrade your system to at least MacOS 10.13.
27+
28+
1129
2023-07-12: End-of-life for CentOS 6
1230
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1331

0 commit comments

Comments
 (0)