Hello everyone!
So the latest code movements and changes on XCMv3 can be tracked here in this GitHub pull request: https://github.com/paritytech/polkadot/pull/4097
But you’ll see that lately there hasn’t been much activity there, and that’s because we’ve also been focusing on another initiative called 2D Weights, which can be followed here: The rest of the way to Weights V2 (Tracking Issue) · Issue #12176 · paritytech/substrate · GitHub
XCMv3 requires us to first implement 2D weights, because we need to accurately calculate how much storage proof size that each XCM occupies in order to better allocate resources into processing them.
Hope this helps!