Hi,

As arranged at the open force last week, we transmitted to the core team a module of ours, which natively adds those two features to any supported module without prior modification required.

It supplies both content staging and content localization to a slave module thanks to a wrapper master module that flows the content data  through several module instances: each version/locale corresponds to its own module id, the wrapper instances then manage their own visibility and permission set, so that the end user only sees a single instance at a time.

I expect that Shaun may provide some feedback about the oportunity to leverage such a solution in the next days.

Cheers