Skip to content

Commit

Permalink
Merge branch 'main' into feat/add_mkswap_switch
Browse files Browse the repository at this point in the history
  • Loading branch information
mikemhenry authored Aug 23, 2023
2 parents fac4400 + d783c10 commit f789129
Show file tree
Hide file tree
Showing 3 changed files with 185 additions and 0 deletions.
83 changes: 83 additions & 0 deletions src/orga/minutes/2023-07-26.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
---
tags: [meeting-notes]
---
# conda-forge core meeting 2023-07-26

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)
- [Last week's meeting](https://hackmd.io/#REPLACE_ME#)

## Attendees

| Name | Initials | GitHub ID | Affiliation |
| ----------------------- | -------- | --------------- | --------------------------- |
| Dave Clements | DPC | tnabtaf | Anaconda |
| Katherine Kinnaman | KK | kathatherine | Anaconda |
| Bianca Henderson | BH | beeankha | Anaconda |
| Keith Kraus | KJK | kkraus14 | Voltron Data |
| Marcel Bargull | MB | mbargull | Bioconda/cf |
| Wolf Vollprecht | WV | wolfv | prefix.dev |
| Jannis Leidel | JL | jezdez | Anaconda/cf |
| Matthew R Becker | MRB | beckermr | cf |
| Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
| John Kirkham | JK | jakirkham | NVIDIA/cf |

12 people total

### Standing items

- [ ]

### From previous meeting(s)

- [ ]

### Active votes

- [ ]

### Your `__new__()` agenda items

- [x] (JK) GLIBC 2.28
- Red Hat source is no longer available, causing pain.
- KJK Alma Linux put out announcement about being ABI compatible.
- MRB: we don't yet know how this is going to shake out. Might be prudent to wait and see who wins.
- How concerned are we with bug-for-bug compatibility
- Some concern, but not enough to hold this back?
- CUDA 12 blocked until this is resolved.
- JK will create an issue
- [x] (MRB) yank conda 23.7 `--json` flag is broken
- This can't be! (Or, it should not have made it through testing)
- https://github.com/conda/conda/issues/12928
- [x] (JK) Windows ARM
- CLA holdup: https://github.com/conda/conda-build/pull/4867
- JL: working towards having CLA conform with governance. Working with NumFOCUS. It's coming!
- Planning to patch feedstock with this change
- [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
- [x] (DPC) [PackagingCon](https://packaging-con.org/) submission deadline is July 31.
- Anyone want to submit something about conda-forge?
- Jaime will submit somthing about conda. Conda-store also coming.
- [x] (DPC) conda-forge presence at NumFOCUS projects meetup in Amsterdam?
- Meeting is 11-13 September, just after DISC, and just before PyData Amsterdam.
- Opening event the night of 10 Sept.
- Collaborative work on 13 Sept
- Most expenses are paid by NumFOCUS.
- Wolf and Jaime will represent conda-forge.
- Jannis is going for conda., but is willing to step aside.
- [x] (WV) sneak peek of pixi
- Pixi fresh look at tooling
- Written in rust on top of rattler.
-
- [ ]
- [ ]


### Pushed to next meeting

- [ ]

### CFEPs

- [ ]
84 changes: 84 additions & 0 deletions src/orga/minutes/2023-08-09.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
---
tags: [meeting-notes]
---
# conda-forge core meeting 2023-08-09

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)
- [Last week's meeting](https://hackmd.io/#REPLACE_ME#)

## Attendees

| Name | Initials | GitHub ID | Affiliation |
| ----------------------- | -------- | --------------- | --------------------------- |
| Matthew R Becker | MRB | beckermr | cf |
| Katherine Kinnaman | KK | kathatherine | Anaconda |
| Chris Ostrouchov | CO | costrouc | Quansight |
| Cheng H. Lee | CHL | chenghlee | Anaconda/cf |
| John Kirkham | JK | jakirkham | NVIDIA/cf |
| | | | |
| | | | |
| | | | |
| | | | |

X people total

### Standing items

- [ ]

### From previous meeting(s)

- [ ]

### Active votes

- [ ]

### Your __new__() agenda items

- [x] (JK) GLIBC 2.28
- ARM / Power
- NVIDA CUDA static libraries (namely cudart) using 2.17 symbols only (others like cudadevrt or culibos use none?)
- (MRB) Should we mark existing glibc 2.28 sysroots as broken? Will submit PR and see what happens.
- SUSE as an option potentially? Will wait and see; still unclear where everything stands
- [x] (JK) Adding `conda-libmamba-solver` to Miniforge
- https://github.com/conda-forge/miniforge/issues/284
- 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 ...
- a) ship `mamba` in Miniforge too
- a2) the above, and deprecate Mambaforge
- and add links that redirect "mambaforge" -> "miniforge"
- use copies to ensure old installs work (if no redirect option)
- 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)
- Discussion: generally have miniconda/miniforge (include conda-libmamba-solver)
- Are we dumping the pypy installers? keep (Up to Matti and others to decide)
- Handling PyPy as separate item (so keeping PyPy installers for now)
- List of artifacts
- https://github.com/conda-forge/miniforge/releases/tag/23.1.0-4
- Consensus is a2
- [x] (JK) TexLive?
- https://github.com/conda-forge/texlive-core-feedstock/issues/84
- We'll need to discover and solve dependency issues before we deprecate (if we choose to do so).
- 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)
- Plan to add README (maybe also `description` in `meta.yaml`) to reset expectations about this package
- Point out release and migrator merged recently
- [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/)).
- 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.
- JRG: Scaleway offers "up to" 2400€/year for OSS projects. M1 runners cost 0.11€/h, so we can afford around 2.5 runners.
- Asked Amit about cirun support for scaleway
- [x] (MRB) Cirrus CI
- Limited free usage due to cryptominers
- Cost is rather high and may involve self-hosting (ToS)
- Running out of credits would mean it would stop suddenly (bad UX story)
- Will look at other options

### Pushed to next meeting

- [ ] (JK) Windows ARM
- [ ] (CHL) How long should we keep `osx-64` support?

### CFEPs

- [ ]
18 changes: 18 additions & 0 deletions src/user/announcements.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,24 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
2023
----

2023-08-24: Bumping Minimum MacOS version to 10.13
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

We will bump the minimum MacOS version from 10.9 (released in Oct. 2013, end-of-life since
Dec. 2016) to 10.13 (released Sept. 2017, end-of-life since Dec. 2020). The main reason we
managed to support 10.9 this long at all, is that conda-forge is able to ship an up-to-date
C++ standard library for OSX, ``libcxx``, superseding the old one present in the MacOS SDK
on the system (at least from the point-of-view of the respective conda environments).

However, several core packages in the ecosystem now require at least 10.13 (or will very soon),
in a way that we cannot be circumvent. These packages include ``libcxx``,
`starting <https://discourse.llvm.org/t/libc-bumping-minimal-deployment-target-for-building-the-dylib-static-library-on-macos/68912>`_
with version 17.0.
This change will not affect already published artifacts, but in the near future, all new builds
for OSX will require at least 10.13. This constraint will be implemented through the ``__osx``
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.


2023-07-12: End-of-life for CentOS 6
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Expand Down

0 comments on commit f789129

Please sign in to comment.