Best practices for A/B tested releases

Looking for some advice around how best to communicate a new feature release that is guarded by an A/B test.

Only 50% of upgraded users will be seeing the new experience.

What would you say are the pros/cons of releasing with updated App Store assets and release notes that discuss this big new feature, but only 50% will be able to see it / use it.

Is it best to wait to release new assets / notes discussing the feature once it's at 100% rollout for all users? Or is it acceptable to release earlier - and have some customers wondering why they aren't seeing it.

Thank you!

Best practices for A/B tested releases
 
 
Q