[Typo3-dev] Versioning Fix

[Robert Lemke]

Hi Kasper,

Kasper Skårhøj wrote:

>> So the question is:
>> Do you think versioning should serve that putpose as well,
> 
> No,
> 
>> or is the
>> above problem (i.e. making a *history* of all changes in records)
>> something *different* to how you understand versioning and should be
>> implemented seperately?
> 
> Yes.

After talking with some developers and customers on the Cebit, I get the
impression that this is not only a specific problem for the wiki. When
people talk about 14.000 pages sites with a team of 14 editors working on
it every day, imagine how many versions you would have after quite a short
time.

In my opinion it makes much sense to use an extra table, the question is
only how difficult it would be to implement it. If it's doable, we should
do it before releasing 3.8.0 because we announce it as a new, stable
feature.

Some other ideas about versioning:

  - In a mini-workflow you would allow an author to only create new versions
    and a chief editor has the right to click the publish button. That's a
    very simple solution which would help in many cases, the only thing
    missing is that currently we cannot disallow an editor to edit a 
    version which is currently online.

    A good solution would be something like "Only allow editing of newer
    versions than the one which is online". The author would still have
    the right to copy an old version to a new one, of course.

  - Almost the same solution but a different reason: There are situations
    when you want to be sure which versions have been online at a certain
    time. To achieve that you have to disallow editing old versions of
    the content.

    When it's very important to have that history, one can even implement
    a feature which sends the content to some official timestamp signing
    authority which adds a timestamp and signs the content. Then you can
    proove that the content existed at a certain time.

  - Versioning is great because you don't have many copies of your CEs
    which you hide / unhide or use the start / stop feature.  However,
    that timing feature (start / stop) is missing for versions: It would
    be nice to be able entering a date when the version will be published
    automatically. Of course an author shouldn't be able to edit such
    a timed version if the chief editor doesn't want to.

For the last feature (timing) we have a sponsor already, so if you consider
this a good feature and have the nerves to implement it, just let me know.

So far for my thoughts about versioning ...

-- 
robert