As a Content Developer or Administrator, I want my content to be versioned, revertable, and pub/unpublishable

[robyurkowski]

I want to be able to do the following things for any type of (conforming) content:

1. Every time I edit a piece of content, the system should create a new revision. I should be able to view these revisions without having to roll back.
2. If I screw up and want to roll back, the system should let me roll back to any point in the history tree (by duplicating it so that the reversion itself is a historied change)!
3. If I roll back to a specific point and then make a revision based on that, the system should append this history as well.
4. If I roll back and want to roll back to the state before I rolled back, I should be able to roll back my roll back. (Cue xzibit meme in comments, I know.)
5. If I delete an item, it moves it to a trash bin, and it is recoverable until I expunge the trash.

Oh. It also has to work with translation.

[parndt]

So basically it's just revisions

[robyurkowski]

That's the joke.

[gogogarrett]

Are we going to have to develop this from scratch? All of the revision libraries I have found rely heavily on active record callbacks.

[robyurkowski]

We will... but fortunately, repository objects should make this very easy to do -- easier than AR in my mind.

[knewter]

Yeah versioning is not a hard problem.