...
The Delete button deletes a selected inactive revision. The Clean up button cleans up all config files which are not referenced by any revision anymore:
Deleting a revision can be useful when there is no more interest in that specific revision, when users will never want to go back to it or check what was / is in there.
It is not possible to delete the active revision.
When older config file(s) or older config file versions are deleted, older revisions that they belonged to will become incomplete, that can also be a reason for deletion.
When a config revision is deleted, only the database record containing the information of the revision which mainly consists of which versions of which config files belonged to that revision, no config files will be deleted and no changes will be made to which config file version will be active.
When older revisions are deleted, some config file versions may not belong to any stored revision anymore.
It can be desirable to remove all these config file versions in one go, for that the Cleanup button has been added.
The cleanup button will first read all revisions and with that information it will check for all existing config file versions whether they are referenced in any of the revisions. If not, they are deleted.
When there are many (large) config revisions the cleanup action can take quite some time without before deleting any config file, just because reading all config revisions can be time consuming.
Even when there are no or hardly any config file versions to delete this can take quite some time.
During the cleanup action the cursor is changed into a waiting icon and for each deleted config file version a message is logged and at the end the total number of deleted config files is logged as well.
Group By
The Group By button will group module config files by their module when selected.
...