Re: release/milestone-based workflow?

Hi Diez,

I haven't implemented it yet but we're working on something that uses two
system folders (Work/Live) inside ZMS and our plan is to use URL rewriting
to "kick" the /work or /live out of all generated urls. Of course this only works
while using Apache in front.

Sincerely
Sebastian Tänzer

-
tänzermedien e.K. - Agentur für Online-Medien
E-Mail: [email protected]  Web: http://www.taenzer.me 
Tel.: 0228-304134-0  Fax.: 0228-304134-99
Kekuléstr. 39, 53115 Bonn, Germany

Am 02.02.2010 um 16:45 schrieb Diez B. Roggisch:

> 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