The creation time plugin uses the wrong date

The last submitted patch, 3: node_revision_delete-revision_creation_time-3447094-3.patch, failed testing. View results →

Updating tests.

Updating tests.

Updating tests. Expecting them to succeed now.

> This is incorrect. A past revision can be changed.

Why should a revision get deleted if it has been updated?

Not sure if that even matters? The plugin is falsely claiming to base a deletion based on the revision creation time, but in fact it's using the changed time (while there's a creation time available).

FWIW, we have a project where we update old revisions retro-actively, when - for example - we add a new (required) fields to the content type.

We have this problem as well. I don't know what caused revisions to have a different updated date than created date, but it makes this module appear to not do what it claims, because in the backend the revisions are listed with the created date being X time ago, but they don't get deleted.

I think that the issue summary details the problem quite well. If are telling the user we are going to delete revisions created older than 2 years and then don't that's a bug.

It feels like we should add a new plugin that uses the updated time and update existing sites to use that and have a created plugin that works as expected. That way sites can choose what they want to do.