Revisioning Module Integration.

Having looked at the code, it appears that this module does not take the "pending" status of the Revisioning and Revision Moderation modules into account. It's more an age-based purge than a status-based purge (which is fair enough). Therefore you have to be careful with the automatic periodic deletion (via cron) as "age" is defined relative to "now" rather than relative to the "live" (current) revision. So you could end up accidentally removing pending revisions, once they're older than the specified age, which may not be desirable.
This could easily be enhanced through a patch.

In manual mode the module does list the pending revisions (as the ones newer than the currently published) and you can choose to delete or not delete them by ticking/unticking the box in front of their revision id.

Hi kiddo,

Agree, it may boil down to a matter of educating your users.

As far as the "current unpublished" revision (i.e. a yet-to-be-published or previously published node) goes, I think you'll be safe (but give a try on a test node).

Because if the module were to delete the current revision (wheter published or not) the data-integrity of the node would be broken. From a database point of view a node simply must have 1 current revision, or the whole thing falls in a heap. So the module would have to make, say, the most recent of the remaining revisions the "current", or alternatively delete the entire node.

Rik