Great work @burhankhanzada. How was your overall experience integrating servo, was there anything specific that you struggled with and might be improved upstream? We'd love to here your feedback.

First thanks for support and asking feedback, although @tronical had already mention cargo version issue one issue i also faced when i was working on windows on arm on my mac with paralles mozjs depnds sccache binariry releases and for windows on arm it was not build so had to solve that in this PR then after solving this make PR in mozjs to also build for windows on arm but i think therse is still issue with sccache and not using version 0.13.0 on mozjs which it will not make windows on arm binaries and servo compile will fail unitl i use my own fork

mozjs doesn't require sccache. sccache is just a tool that is used in the CI of mozjs to cache compilation results. Locally it should build just fine without sccache.

In principle you also don't need precompiled artifacts for mozjs-sys - although it can make things easier in terms of setting up the environment and . We don't do any upstream testing of servo on arm64 windows though, so there can of course be hidden issues.

@burhankhanzada We are currently preparing the servo 0.1.0 release, which will also be available on crates.io (We already published servo 0.1.0-rc2). Would you consider updating to that, and letting us know if you encounter any problems?

We are also planning for servo 0.1 to be an LTS release (preliminary description of LTS scope), since we thought some embedders might prefer doing major upgrades on a half-yearly schedule rather than every month, but still like to receive security relevant updates (presumably mainly from spidermonkey, the JavaScript engine)

@burhankhanzada We are currently preparing the servo 0.1.0 release, which will also be available on crates.io (We already published servo 0.1.0-rc2). Would you consider updating to that, and letting us know if you encounter any problems?

We are also planning for servo 0.1 to be an LTS release (preliminary description of LTS scope), since we thought some embedders might prefer doing major upgrades on a half-yearly schedule rather than every month, but still like to receive security relevant updates (presumably mainly from spidermonkey, the JavaScript engine)

Sure @jschwe thanks for the LTS efforts, I am happy to try that out and let you know if i encounter any problems.

I have updated dependency as #11317 to crates.io v0.1.0-rc2 and havent got any issues looks good thanks.