You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@nschonni I think raising Alpine/musl has been waiting on more active contributors/collaborators working to support it. (ie who would be our go-to people to involve when there are problems/issues that need to be resolved) I'm not sure I've seen that change substantially.
The @nodejs/docker folks are pretty on-the-ball wrt Alpine builds, although I'm not sure there's anyone on there that wants to be on the hook to support core when things break. We do already have Alpine in our CI mix so breakage is already something we look for with every commit and it's been pretty stable, so I think it might even already qualify for Tier 2:
Tier 2: These platforms represent smaller segments of the Node.js user base. The Node.js Build Working Group maintains infrastructure for full test coverage. Test failures on tier 2 platforms will block releases. Infrastructure issues may delay the release of binaries for these platforms.
@nodejs/docker do we have any people willing to be put on a @nodejs/musl group to be go-to if/when weird musl things break that nobody else has expertise or setups to debug?
Its that time of year again
What we build and test on
From https://github.com/nodejs/node/blob/master/BUILDING.md#official-binary-platforms-and-toolchains
Compiler levels
Actions
I dont think theres much to do this time around? cc @nodejs/build
The text was updated successfully, but these errors were encountered: