release/milestone-based workflow?

Hi,

I know I can somehow hack this together, but I'd rather ask here before: for 
my company, we often have orchestrated releases, where large volumes of 
content are created, and then released at a specific point. For example if 
the new version of Ableton Live comes out, this is accompanied by massive 
website changes.

Of course in the meantime, content-editor need to view the page in the 
upcoming version, and then, on a specific date or by manually flipping a 
switch, this stuff is live.

So I was wondering if anybody here has implemented such a thing already & can 
share experiences?

Thanks,

Diez