- Woa-wg - lists.corecollective.dev

Reminder: CoreCollective Hub mailing list replaces the Google Group
by Nathalie Chan King Choy (Windows on Arm) 23 Oct '26

23 Oct '26

Hi all, Reminder that windows-on-arm(a)corecollective.dev is the old Google Group. It will forward to the hub list for now, but we may turn it off in the future. woa(a)*hub*.corecollective.dev is the CoreCollective hub mailing list. The server should now be configured for DMARC and DKIM to improve receive rates. Please reach out to me directly if you find that all the hub emails are going to your spam folder & we can try to debug. Thanks & best regards, Nathalie --- CoreCollective Community Manager Android & WoA working groups

1 0

Re: Python Windows on Arm ecosystem report
by Grant Likely (Windows on Arm) 22 Oct '26

22 Oct '26

No, the tracker isn’t pulling anything from Gleb & Omair’s tracker, but that can be changed or it be merged in. I certainly don’t want to create competing trackers! This was created via a few hours of quality time with an AI assistant. It is designed to be run periodically. I’ve not pushed it out to Github or anywhere else yet where it could be done with a regular CI job. Gleb, how is your tracker being kept up to date? I can see that there is some testing performed. The report I posted only covers availability of wheels for the top 1000 packages. It doesn’t do any testing. The package status bit looks like I’ve duplicated work, but the research on reasons why could be integrated in. g. From: "Grant Likely (Windows on Arm)" <woa(a)hub.corecollective.dev> Date: Wednesday, 21 October 2026 at 19:25 To: Marcus Perryman <marcus.perryman(a)microsoft.com> Cc: Grant Likely <Grant.Likely(a)arm.com>; CoreCollective Windows on Arm <windows-on-arm(a)corecollective.dev>; Gleb Khmyznikov <gkhmyznikov(a)microsoft.com> Subject: [CoreCollective WoA] Re: Python Windows on Arm ecosystem report Hi Grant, Does your report include awareness of data in these trackers created by Gleb & Omair, or are you going direct from projects? https://github.com/khmyznikov/PyEnv-WoA-State/issues/1 https://omjavaid.github.io/wheels-on-arm/ Thanks & regards, Nathalie On Wed, 21 Oct 2026 at 11:18, Marcus Perryman <Marcus.Perryman(a)microsoft.com<mailto:Marcus.Perryman@microsoft.com>> wrote: +Gleb This looks good, thx Grant. Could we run this periodically to get a track of the direction things are going? From: "Grant Likely (Windows on Arm)" <woa(a)hub.corecollective.dev> Sent: 21 October 2026 11:16 To: Marcus Perryman <Marcus.Perryman(a)microsoft.com<mailto:Marcus.Perryman@microsoft.com>>; Nathalie Chan King Choy <nathalie-ckc(a)linaro.org<mailto:nathalie-ckc@linaro.org>>; CoreCollective Windows on Arm <windows-on-arm(a)corecollective.dev<mailto:windows-on-arm@corecollective.dev>> Subject: [CoreCollective WoA] Re: Python Windows on Arm ecosystem report Hi Marcus From the call yesterday I pulled together a tool that generates an ecosystem report. Is this the sort of data you’re looking for? This is for the top 1000 packages. It is easy to adapt the search criteria from here and also dig into more details on the blockers. Everything here is based on public data. It isn’t an exhaustive search. https://claude.ai/artifact/KiRoGa9rGDtwMKTggsaWYc Grant -- Grant Likely Arm Fellow and CoreCollective Technical Chair IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- You received this message because you are subscribed to the Google Groups "(Deprecated) CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/AM0PR….

2 1

Windows on Arm runners
by 'Marcus Perryman' via (Deprecated) CoreCollective Windows on Arm (Windows on Arm) 22 Oct '26

22 Oct '26

Does your project use Windows on Arm standard Github runners? You could save up to 20% runner time The github standard runners for Windows on Arm do all their work on the C: drive which is an Azure attached storage drive and the system NTFS drive. These VMs have access to an NVMe 220GB drive which remains unconfigured (raw) in the current image. There is an active request to the GH team to modify these images to configure the drive and move the _work area - with some additional optimizations - here: [Windows] All Windows runner images should be using ReFS for the action_runners folder and cache locations * Issue #14878 * actions/runner-images<https://github.com/actions/runner-images/issues/14878> (feel free to add comments and requests to ship this). While this remains unresolved there is a simple change that can be applied to a build script that can deliver CI wall-clock reductions of 10-20%. See this PR for IronRDP that improved the CI time by 10% (your mileage will vary!) https://github.com/Devolutions/IronRDP/pull/2186 What does it do? Find the raw drive, create a new partition and format as ReFS (Dev Drive). Junction the new drive under the actions-runner as the _work folder. For IronRDP it also adjusts the cache location for cargo packages as these will benefit from the additional performance. All this is gated by tests for Arm runner, github-hosted and the exitence of the raw partition, so if GH ship fixed images it will just no-op. Marcus -- You received this message because you are subscribed to the Google Groups "(Deprecated) CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/FRZPR….

1 0

Re: Python Windows on Arm ecosystem report
by 'Marcus Perryman' via (Deprecated) CoreCollective Windows on Arm (Windows on Arm) 22 Oct '26

22 Oct '26

+Gleb This looks good, thx Grant. Could we run this periodically to get a track of the direction things are going? From: "'Marcus Perryman' via (Deprecated) CoreCollective Windows on Arm (Windows on Arm)" <woa(a)hub.corecollective.dev> Sent: 21 October 2026 11:16 To: Marcus Perryman <Marcus.Perryman(a)microsoft.com>; Nathalie Chan King Choy <nathalie-ckc(a)linaro.org>; CoreCollective Windows on Arm <windows-on-arm(a)corecollective.dev> Subject: [CoreCollective WoA] RE: Python Windows on Arm ecosystem report Hi Marcus From the call yesterday I pulled together a tool that generates an ecosystem report. Is this the sort of data you're looking for? This is for the top 1000 packages. It is easy to adapt the search criteria from here and also dig into more details on the blockers. Everything here is based on public data. It isn't an exhaustive search. https://claude.ai/artifact/KiRoGa9rGDtwMKTggsaWYc Grant -- Grant Likely Arm Fellow and CoreCollective Technical Chair IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- You received this message because you are subscribed to the Google Groups "(Deprecated) CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/FRZPR….

3 2

Notes: 2026-10-20 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 21 Oct '26

21 Oct '26

Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* - Adhemerval Zanella, Linaro - Evgeny Karpov, Arm - Gleb Khmyznikov, Microsoft - Grant Likely, CoreCollective - John Stubley, Arm - Julianus Larson, CoreCollective - Marcus Perryman, Microsoft - Nathalie CKC, CoreCollective - Omair Javaid, Linaro - Rick Duong, Arm - Stephanie Leong, Arm - Thomas Dunkle, Arm *Links shared in chat:* - GNU Toolchain experimental weekly builds for Windows on Arm64 are publicly available on GitHub. - https://github.com/arm/gnu-toolchain-for-windows-on-arm64 - https://github.com/arm/gnu-toolchain-for-windows-on-arm64/actions/runs/3931… - Celebrating Python 3.15 release (Blog posts, LinkedIn posts) - https://developer.arm.com/community/arm-community-blogs/b/announcements/pos… - Python 3.15 delivers a native-by-default experience on Windows on Arm - Windows Developer Blog <https://blogs.windows.com/windowsdeveloper/2026/10/14/python-3-15-delivers-…> - Native Python on Windows on Snapdragon: a stronger foundation for developers and AI workflows <https://www.qualcomm.com/developer/blog/2026/10/native-python-windows-on-sn…> - Python 3.15: New Features for Data Scientists <https://www.anaconda.com/blog/python-3-15> - https://windowsreport.com/microsoft-brings-native-python-support-to-windows… - https://mangodeveloper.com/articles/python-3-15-windows-on-arm-native-by-de… - https://windowsforum.com/news/python-3-15-makes-windows-on-arm-native-first… *AI Notes - please notify us of inaccuracies:* Meeting Overview - Toolchain progress updates, covering the public availability of experimental GNU toolchain builds for Windows on Arm64 and timelines for native compilation and Cygwin cross-toolchains. - Celebration of Python 3.15 native-by-default release on Windows on Arm, cross-organizational collaboration, and ongoing efforts to automate ecosystem package tracking. - Ecosystem status updates, PyArrow maintainer funding, alongside native PostgreSQL support status inquiries. Decisions/Key Takeaways - Approvals were completed and the public repository for experimental GNU toolchain weekly builds for Windows on Arm64 is live on the Arm GitHub organization, currently providing cross-toolchains for Linux and macOS. - Python 3.15 has officially achieved native-by-default support on Windows on Arm. - Python package ecosystem maintenance tracking: What we have for Cryptography could be extended to compare WoA vs Windows x86 build status at scheduled interval & flag discrepancy for investigation. - httptools and mysqlclient libraries have been enabled for Windows on Arm since the previous meeting. - PyArrow: Fathi from Linaro fully occupied on other projects, so responding on his patches would take a while --> can hand off to Microsoft team that has availability - [Deferred] Maintainer funding for PyArrow still under discussion. Action Items - *Gleb K.* - Share the what he has for the automated GitHub Actions wheel build monitoring. - (DONE) Send an email to the internal Microsoft team to coordinate the PyArrow handoff from Linaro. - *Grant L.* - (Shared for feedback <https://claude.ai/artifact/KiRoGa9rGDtwMKTggsaWYc>) Build a prototype tool or dashboard to automate tracking of Python package Arm enablement and maintainer maturity. - *Nathalie C.* - Add links to LinkedIn posts regarding the Python 3.15 release into the meeting notes. *Here they are:* - - *Rick's* <https://www.linkedin.com/posts/rickduong_great-news-python-315-now-fully-su…> - *Arm's* <https://www.linkedin.com/feed/update/urn:li:activity:7516276684438884352/?h…> - *Devang's* <https://www.linkedin.com/posts/devangaggarwal_ai-python-snapdragon-share-75…> - *Gaurav's* <https://www.linkedin.com/posts/gauravnimi_snapdragon-python-python-share-75…> - *Nicole's* <https://www.linkedin.com/posts/nicolemichaelis1_great-to-see-python-315-mak…> - *Anaconda's* <https://www.linkedin.com/posts/python-315-is-here-and-so-is-native-python-s…> - *Thomas D.* - Reach out to Mayank to get the latest status on native PostgreSQL support for Windows on Arm and request inclusion in communications with Dave Kramer. - *Evgeny K.* - Consult with Andre regarding merging experimental toolchain builds into official GNU releases once production quality is reached. For Future - Patches for native toolchain compilation are scheduled for submission by the end of November, with upstreaming targeting December or January. - Delivery of a native toolchain for MinGW and a cross-toolchain for Cygwin is targeting end of the year. - Fathi may return to address comments on his PyArrow patches in the future once current project commitments conclude. - Ecosystem enablement topics & outstanding PR list to be discussed in a future meeting when Mayank is available. Notes - *GNU Toolchain Updates* - Toolchain builds for Linux and macOS are currently available for download. - Arm has received all necessary approvals and published the experimental GNU toolchain repository on the Arm organization on GitHub . - Weekly experimental builds are automatically generated every Saturday directly from upstream commits without downstream patches. - Upstreaming of patches for native compilation is tracking for submission by late November, with upstream integration expected in December or January. - Delivery of a native toolchain for MinGW and a cross-toolchain for Cygwin is targeted by the end of the year to streamline testing and unblock GNU-dependent downstream projects. - *Python 3.15 Native-by-Default Release* - Python 3.15 is now native-by-default on Windows on Arm, marking a major milestone for ecosystem maturity. - The achievement was recognized as a prime example of successful cross-industry collaboration among Microsoft, Arm, Qualcomm, and Linaro via CoreCollective. - Native execution delivers efficiency benefits across Windows on Arm environments, especially for developer tooling and agentic workflows that routinely spin up Python. - Ongoing efforts will focus on Python package enablement, though full parity with x64 is not required given legacy and obsolete packages. - *PyArrow * - Upstream PyArrow maintainers lack funding for review bandwidth. The community has sufficient engineering resources to submit lots of PRs. - Microsoft is evaluating funding mechanisms internally to help alleviate maintainer bandwidth constraints, with outcomes pending. - Linaro engineering contributions from Fathi have paused due to his full allocation to other projects, though he may return to address feedback comments on his patches later. - Microsoft has an internal engineering team prepared to take up PyArrow work, and Gleb K. will make the intro for hand-off from Fathi via email. - *Python Package Ecosystem Automation and Tracking* - Microsoft is developing an automated workflow to monitor approximately 80 packages with wheel builds that have GitHub Actions, expanding on the monitoring model used for cryptography. - Workflows will run on a schedule comparing Windows on Arm builds against Windows x86 builds. - Any failure specific to Windows on Arm will trigger automated issue updates across package-specific tracking issues under a master issue . - Overall top 1000 downloaded package enablement currently stands at 86%, which is down from before because the top 1000 list is based on downloads, so WoA-enabled packages might drop off & new ones replacing them. httptools and mysqlclient enabled since the prior meeting. - Grant L. will prototype an automated dashboard to track package maturity from initial enablement to maintainer-owned maintenance, avoiding manual tracking across repositories. - *PostgreSQL Native Support* - Arm received another internal request regarding native PostgreSQL support on Windows on Arm. - The most recent correspondence between Mayank and Dave Cramer at PostgreSQL indicates Dave does not directly manage Arm build generation, leaving unresolved technical issues as of September 2026. - Native PostgreSQL progress remains stalled after initial assessment 18 months ago; Thomas D. will follow up with Mayank to obtain current status and join the discussion thread.

1 0

Agenda: 2026-10-20 CoreCollective Windows on Arm Technical (Daylight Savings)
by Nathalie Chan King Choy (Windows on Arm) 19 Oct '26

19 Oct '26

Hi all, Here are the topics that I have collected so far for 2026-10-20 : - Python - Celebrating Python 3.15 release (Blog posts, LinkedIn posts) - PyArrow maintainer funding gap - Project to enhance trackers/gather data to scope effort for long-term maintenance - GCC/LLVM - Enablement - Mayank: PRs needing community support to get maintainer traction - Git for Windows: Could Mayank share builds from fork to WG for early feedback? Please let us know if you have additional topics. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups

1 0

Notes: 2026-10-06 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 08 Oct '26

08 Oct '26

Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* - Adhemerval Zanella, Linaro - Anthony Roberts, Linaro - Don Harbin, CoreCollective - Evgeny Karpov, Arm - Fathi Boudra, Linaro - Gleb Khmyznikov, Microsoft - John Stubley, Arm - Julianus Larson, CoreCollective - Marcus Perryman, Microsoft - Mayank Agrawal, Qualcomm - Nathalie CKC, CoreCollective - Omair Javaid, Linaro - Paul Black, Arm - Rajath Holla, Nvidia - Rick Duong, Arm - Saket Jha, Microsoft - Stephanie Leong, Arm - Thomas Dunkle, Arm *AI Assisted Notes - please notify us of inaccuracies:* Meeting Overview - Overview of Python 3.15 release timing, ecosystem blog post alignment, and long-term package maintenance strategy. - Status updates on GCC, LLVM, Cygwin porting, and native Git for Windows Bash enablement. - Review of Anaconda roadmap progress, Rust performance optimizations, and Works on WoA site data accuracy for Android Studio. Decisions/Key Takeaways - Python: Maintain Nvidia's shortlist of 6–7 libraries as a standing agenda item for technical meetings to track post-3.15 ecosystem progress. - Shift the primary technical meeting focus from Python ecosystem enablement to tracking native Git for Windows Bash delivery. - Great work team! Look out for Python 3.15 release blog posts by member companies at the earliest on Monday following the official Python release. Many will celebrate accomplishment on LinkedIn. Action Items - [Evgeny K.] - Share the updated GCC weekly builds repository link with Nathalie C. once security review is complete. - [Gleb K.] - Send the Nvidia shortlist of 6–7 Python libraries to Nathalie C. for inclusion in the working group's tracking list. - [Marcus P.] - Check in with Steve on Thursday regarding the final Python 3.15 release date. - Contact Nicole at Anaconda to obtain the latest status update on their Windows on Arm roadmap. - [Mayank A.] - Ask Qualcomm testing team to do a more thorough test of Android Studio & correct its status on worksonwoa.com. - [Nathalie C.] - Add Nvidia's Python library shortlist to the technical meeting tracking list upon receipt from Gleb K.. - Follow up with Gaurav in tomorrow’s steering committee call regarding Android Studio. For Future - Upstream Cygwin porting work is targeted for completion by the end of November 2026 - It would be great if we could target to have native Git for Windows for release by the end of calendar year 2026. Potentially feasible. - Anaconda is targeting the end of their year for their roadmap deliverables. - Linaro plans to deploy a local SPEC-based release testing framework for Windows on Arm within a few months. Notes - [Welcome & Announcements] - Stephanie Leong (new at Arm) is focusing on strategic partnerships and ecosystem at Arm & one of the areas of her focus is WoA. - CoreCollective published a Spotlight post about the WoA working group <https://corecollective.dev/blog/wg-spotlight-woa/> and distributed the link to the mailing list. - Nvidia released a public CUDA build of PyTorch that runs on Arm. - [Python 3.15 Release & Long-Term Maintenance] - Python 3.15 changes default Windows on Arm installations via the Python manager from X64 to Arm64 builds. - The release is delayed by approximately one week due to Python maintainers adding an extra RC build. - Synchronized blog posts from Microsoft, Qualcomm, Anaconda, and CoreCollective will publish on the Monday following the official release. - Next 3 months members will work on remaining key packages, including Nvidia's shortlist. - Linaro funding for Python work ended on September 30; future sponsorship discussions are in progress. - [Anaconda Roadmap check-in] - Anaconda: Moving Windows on Arm wheels from an experimental branch to the main branch, enabling native package installation via Conda without custom flags. - Need to confirm with Anaconda if their target completion timeframe is the end of the year. Marcus will reach out to Nicole for latest status. - [GCC, Cygwin & Native Git for Windows] - GCC merged the auto-import implementation upstream, fixing dynamic linking relocation blockers for Cygwin, MinGW, and native toolchains. - GitHub repo for weekly builds: repo is prepared & going through security review (target completion by end of next week). Daily testing builds from upstream are running for Linux and macOS hosts. - Git for Windows Bash prototype is functioning using MSYS2 and cross-compilers; final upstreaming requirement from maintainers is to use the native toolchain. Target end of November. - [LLVM, Rust & Performance Optimization] - Enabling PGO and LTO in Rust demonstrated significant performance improvement on Windows on Arm. - However, enabling LLVM PGO/LTO increased CI build times from 5 hours to 8 hours, exceeding the 6-hour gate; Microsoft is evaluating hardware options and optimizations. - Linaro is developing a SPEC-based release testing framework for LLVM while maintaining existing buildbots. - [Works on WoA & Android Studio] - Android Studio is currently listed as "supported under emulation" on worksonwoa.com based on Qualcomm verification data. - While the IDE application launches, Microsoft testing found it unsuitable for full end-to-end development. Mayank will ask their tester to re-test

1 0

Agenda: 2026-10-06 CoreCollective Windows on Arm Technical (Daylight Savings)
by Nathalie Chan King Choy (Windows on Arm) 04 Oct '26

04 Oct '26

Hi all, Here are the topics that I have collected so far for 2026-10-06 : - Python - Python long-term maintenance and CI tracking: Could we have the developers who enabled WoA in upstream let the respective project maintainers know about CC WoA WG GitHub issue tracker? - Follow-up: 8/25 call Anaconda roadmap status was that conda and Miniconda support for Windows on Arm is not expected to be completed before October. Any schedule clarity now that we’re in October? - GCC/LLVM - Enablement Please let us know if you have additional topics. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups OOO 10/5. At a conference 10/6-10/9 (replies may be delayed)

1 0

WoA Spotlight Blog is Live!
by Don Harbin (Windows on Arm) 30 Sep '26

30 Sep '26

Hi WoA WG Members, I wanted to share that the WoA Spotlight blog is now live! It can be found on the website at https://corecollective.dev/blog/wg-spotlight-woa/ We’d love your help spreading the word—cross-posting or resharing on your own channels would be fantastic! It's also been posted to the CoreCollective LinkedIn channel here <https://www.linkedin.com/posts/corecollective-dev_windowsonarm-opensource-s…> . Please take a moment to *like and reshare the post*. And if you aren't following CoreCollective on LinkedIn yet, be sure to give us a follow! Best regards, Don Harbin | *Community Director* don <don.harbin(a)linaro.org>@corecollective.dev |

1 0

Notes: 2026-09-22 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 22 Sep '26

22 Sep '26

Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* Anthony Roberts, Linaro Don Harbin, CoreCollective Evgeny Karpov, Arm Fathi Boudra, Linaro Grant Likely, CoreCollective Julianus Larson, CoreCollective Matt Allard, Nvidia Mayank Agrawal, Qualcomm Nathalie CKC, CoreCollective Omair Javaid, Linaro Paul Black, Arm Rajath Nvidia, Nvidia Rick Duong, Arm Saket Jha, Microsoft Thomas Dunkle, Arm *AI Notes - please notify us of inaccuracies:* Meeting Overview - Discussed project estimates and updates for Python packages, including PyArrow and Snowflake. - Reviewed infrastructure migration and funding status for LLVM, along with GCC, GNU Fortran, Cygwin, and MinGW updates. - Analyzed enablement blockers for Open3D and Embree on Arm64 MSVC. Decisions/Key Takeaways - Anthony's assessment is that Gleb's PyArrow estimates are accurate with minimal that is parallelizable - LLVM buildbots for Windows on Arm are successfully running on new staging infrastructure and will be migrated to production in a couple weeks . - At end of funding for Linaro to do LLVM work for WoA. Would require partner funding to continue additional LLVM technical work and PGO benchmarking. If interested, reach out to Omair to discuss further. - Arm's GNU Fortran experiment: achieving a ~70% pass rate with OpenMP. Action Items - *Evgeny* - - Once released, notify Nathalie to announce the public Arm weekly builds repository on the CoreCollective WoA WG webpage news section and potentially add it to the CoreCollective GitHub page. - *Mayank A.* - Wait for Embree to issue an official release, update the vcpkg hashes and packages once available, and ping the Open3D maintainer regarding the pull request - Consolidate the updated list of pull requests requiring review/support and send it to the mailing list. - Saket - Check with Gleb regarding feedback on Python package priorities when he returns. - Omair - Complete testing of the new Windows on Arm LLVM build bots and migrate to production in a couple of weeks. Notes - *Participant Introductions* - Matt A. introduced himself as part of the NVIDIA client product team, managing ISV partner software readiness for creative, streaming, and workstation applications. - *Python Ecosystem* - Anthony evaluated PyArrow estimates provided by Gleb K., confirming a timeline of 16 to 18 weeks (including reviewer turnaround) . - Fathi B. submitted merge requests for PyArrow (currently paused) and for adding Arm64 wheels for the Snowflake Python connector. - Next Python package prioritization is awaiting feedback from Gleb K. upon his return. - The upcoming Python 3.15 release remains on track for next week, with internal release blog materials under review. - *GCC and LLVM* - Omair J. reported that LLVM buildbots for Windows on Arm have been migrated to new staging infrastructure and are operating smoothly. - Evgeny K. noted GNU Fortran configuration adjustments reached a ~70% pass rate with OpenMP. Not planning to proceed further at this time. - Evgeny K. is preparing a revised Cygwin patch for Binutils expected next week to replace an insufficient patch from a Git for Windows contributor. - Cygwin regression fix is under mailing list discussion, while a MinGW regression was reported and resolved by the community. - An auto-import patch supporting dynamic linking in Binutils is on the mailing list and expected to merge by the end of Q3. - *Application Enablement* - Mayank A. reported that Open3D relies on vcpkg, which lacks an official Arm64 MSVC release of Embree. - While Embree supports Arm64 via ClangCL, MSVC support requires unreleased changes. (Embree on Arm64 has been functional in Blender since 2024 when compiling with ClangCL, but compiling via MSVC through vcpkg fails for Open3D. The blocker is specifically Arm64 MSVC support—which exists in the code repository but is not yet included in an official release tag or vcpkg) - Progress on Open3D/NPM enablement is blocked until an official Embree release is published and vcpkg hashes are updated. - *Steering Committee Preparation* - Tomorrow's Steering Committee meeting agenda will focus on coordinating alignment for the upcoming release.

1 0