A
Alexwilmac
I find great that OBH, since 1.0.x has added the version name to the backup filenames.
Only, in order to have an absolute alphabetical order reflecting the DATE ORDER, I'd consider to put the data as a prefix and not a suffix.
So, instead of
OBH-Solo4k-release-4.1.033-20180817_060000
I propose to developers
OBH-Solo4k-20180817_060000-release-4.1.033
or, even more readable
OBH-Solo4k-2018-08-17_06_00_00-release-4.1.033
(where the first part of the filename, OBH-Solo4k-release is the way I set).
Imagine one would like to do some experiment and would add something to the filename, but still saving the date order as the main info, you'll have something like that
OBH-Solo4k-2018-08-17_10_00_00-NEW_conf_release-4.1.033
and the DATE order would be safe because you'll have:
....
OBH-Solo4k-2018-08-18_06_00_00-release-4.1.033
OBH-Solo4k-2018-08-18_10_00_00-NEW_conf_release-4.1.033
....
Only, in order to have an absolute alphabetical order reflecting the DATE ORDER, I'd consider to put the data as a prefix and not a suffix.
So, instead of
OBH-Solo4k-release-4.1.033-20180817_060000
I propose to developers
OBH-Solo4k-20180817_060000-release-4.1.033
or, even more readable
OBH-Solo4k-2018-08-17_06_00_00-release-4.1.033
(where the first part of the filename, OBH-Solo4k-release is the way I set).
Imagine one would like to do some experiment and would add something to the filename, but still saving the date order as the main info, you'll have something like that
OBH-Solo4k-2018-08-17_10_00_00-NEW_conf_release-4.1.033
and the DATE order would be safe because you'll have:
....
OBH-Solo4k-2018-08-18_06_00_00-release-4.1.033
OBH-Solo4k-2018-08-18_10_00_00-NEW_conf_release-4.1.033
....