[Question] Would the maintainers like to be added to libc++'s special vendor communications? #2411
Comments
|
By the way, I did some more research and realized that you folks didn't get a proper deprecation notice, which could explain why bf46c8a was done almost one year after the deprecation should have been noticeable. I explained what happened here: llvm/llvm-project#134425 |
|
I personally would like to be added. |
|
I also would like to be added. Thanks. |
|
Ack! I see that only members of the LLVM organization can be added, but I've reached out to an admin of the LLVM org to see what we can do about that. |
|
Ok, you can request "Triage access" by following the steps here: https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access Specifically, when you create an issue to ask for "commit access", you can mention that you're seeing "Triage access" and CC me on that issue. |
Hi,
I came here through some thread that discussed how React Native wasn't building anymore with Xcode 16.3, which led me to Folly since the React Native fix was to update their Folly dependency to include bf46c8a.
Libc++ has a special Github group we use to communicate with vendors and important open source projects about upcoming breakage. This complements our existing release notes and deprecation cycles (using deprecation warnings to tell people about upcoming breakage), and it happens earlier in the cycle (when or even before we merge PRs). That group is very low traffic, we ensure to only ping the group when we expect potential fallout from a change. The goal here would be to ensure that Folly developers can see such breakage coming well in advance.
Please let me know if you would like to be added to that group, and if so which Github username(s) should be added. Thanks!
The text was updated successfully, but these errors were encountered: