How to manage new version of wiki

summary:

If I'm working on changes to my wiki, affecting several pages, and I want them all to be kept on hold until a certain "release" day, how should I manage this?

How to manage new version of wiki

Pgr 1210522048|%e %b %Y, %H:%M %Z|agohover

(please read the summary)

In short, I would like to prepare "future versions" of several pages, and then have them go public all at once (specifically, when the software I'm documenting is released in a new version).

Of course I could copy all pages to a sandbox, then do all changes inside the sandbox, and them copy each page back one by one, on the day of release, but is there a smarter way to do it?

I also thought about creating the new version of each page, but immediately reverting to the old version. Then I would do this for every page, and finally on the release day, I would go back and revert to the new version on each page.

Any better ideas?

Re: How to manage new version of wiki

Craig Macomber 1210536763|%e %b %Y, %H:%M %Z|agohover

One approach would be to put all the new versions in a different category (named after the version number) and just not link to them. Once everything is ready, switch the links over so the new documents are seen. If we had the ability to hide categories (maybe in the upcoming promised improved permissions system), this would work even better.

Re: How to manage new version of wiki

Pgr 1210542649|%e %b %Y, %H:%M %Z|agohover

Hhmm.. thanks for the suggestion, but I see some disadvantages there… for one, I would like to keep the full history of each page, so creating new pages and then changing the links isn't good for this.

Also, if I have to change a lot of pages (and this is the case), going around changing the links is going to be a lot of work, and will ruin the organization of the site…

Any more suggestions? Maybe there's just no good way to do it… :-(

Re: How to manage new version of wiki

Craig Macomber 1210544184|%e %b %Y, %H:%M %Z|agohover

One possibility is to simply make the changes, then revert to the old version. When it comes time to update, restore it back to the new one.