Repository navigation
Support Tiers: document future macOS support - #20497
Conversation
a3a37e8 to
55eee94
Compare
17f7300 to
cc1f7f0
Compare
21628dc to
e361886
Compare
There was a problem hiding this comment.
OK with this, with a couple points:
- Is September 2025 too soon given we just released 4.6.0 and this would require a 4.7.0? Could easily be October/November if so - doesn't need to be perfect years.
- Pretty cautious about promising 2026 given there's little technical reason for it but otherwise have no strong opinion there
Sept 2027 however does align perfectly with when Intel Homebrew/core CI will likely no longer be feasible (assuming macOS 26 Intel CI isn't possible for us which I'll find out next month)
@Bo98 I guess I was thinking (and could clarify with any suggested wording?) with this document these were "no sooner than X" dates rather than "definitely on X" dates.
Not sure what cautious/technical reasons bits mean here; what if anything do you think might be worth changing/reconsidering in 2026? Not sure I understand, sorry!
Cool. I'd rather we're not sitting on September 2028 to drop Intel support, though. I like the idea of dropping it one Tier at a time over the next two years. Could potentially push out until later in the year each time if that made sense, though? |
OK with all of this then if it means this. It initially read to me like "definitely on X". |
e361886 to
528f7f5
Compare
Added a |
Let's provide a clear roadmap of what we plan to support, not and when we plan to make these changes. Co-authored-by: Sam Ford <[email protected]> Co-authored-by: Eric Knibbe <[email protected]>
45341e4 to
31e212b
Compare
| Here's the timescale for planned future Tier support: | ||
|
|
||
| - Today (August 2025): | ||
| - Tier 1: macOS Sequoia 15, Sonoma 14, Ventura 13 on Apple Silicon and Intel x86_64 |
There was a problem hiding this comment.
I believe we aren't currently building intel bottles for Sequoia due to the difference between the values of NEWEST_HOMEBREW_CORE_MACOS_RUNNER and NEWEST_HOMEBREW_CORE_INTEL_MACOS_RUNNER in github_runner_matrix.rb
are there plans to build Intel x86_64 bottles on Sequoia or Tahoe during this next year?
I can open a separate issue / discussion if this is the wrong place to ask this
There was a problem hiding this comment.
We are only building Intel bottles on Sequoia where required (pkgconf, gcc, etc.), otherwise those systems use the Sonoma bottles. This will continue with Tahoe.
There was a problem hiding this comment.
Exact plans for CI is mostly speculative at this point as it's still TBC how feasible Tahoe Intel bottling is (even for gcc etc) due to limited hardware support. I'll be confirming plans when the RC drops and I'm able to test things on our CI. We may do a slow-fill of Sequoia when we drop Ventura (or initially at least expand to cover things that need newer Xcode) but that will likely be the only time that'll happen and will give us 2 years to handle the end of Homebrew/core Intel CI, which aligns with the 2027 date we are targeting.
|
The proposed eventual drop of all intel macs is concerning when https://github.com/dortania/OpenCore-Legacy-Patcher is successfully keeping all my old macs alive, up to date, and my working machines as I, and many Indonesians who I ship old devices too, cannot afford new machines, nor need the additional power or capabilities when our current machines are plenty capable enough, and have no desire to promote ewaste. Can homebrew commit to supporting the lastest macos version supported by opencore legacy patcher; and only when opencore legacy patcher drops support for intel macs, then drop support. Alternatively, how about the ability to crownsource the builds of bottles? So homebrew can drop support from their official infrastructure, however sys admins can set an environment variable to tell homebrew to upload its builds to a URL which homebrew then queries in the future. |
|
Devices using OCLP are already considered Tier 2 or Tier 3. Managing ewaste and legacy systems is not a goal of the Homebrew project. Providing the latest software on supported systems is a goal of the Homebrew project. Users can create their own taps and support whatever builds they want, but we will not consider them official or recommend them. It should also be noted that GitHub is ending support for Intel macOS runners in August 2027, around the time we are dropping support as well. At that point, the community will need to figure out what they want to do, as the largest source of free CI will be gone, and new versions of Homebrew will not run on Intel systems. |
|
@balupton As-of September 2026, MacPorts will likely be a better fit for those Macs than Homebrew. |
Let's provide a clear roadmap of what we plan to support, not and when we plan to make these changes.