Purge old file versions

[jclausius]

That makes sense. I've added your latest comments to this work item (F:10226). The hard thing about this would be to update all historical versions of folders that it no longer contains a file... Or perhaps those get changed into stubs of NULL entries. This feature is a bit complicated as coding around history changes can be messy and needs to be careful as one would still need to be able to view/get from a historical version of a folder.

I did come across a different feature request to store ONLY the latest of a file... In other words, a file would have no history, and only keep the latest version. But I don't think that would apply in your case, since you might need DLLs from 1 yr ago. Only mentioning it to see if you feel any comments need to be added to that request.

[BigBrett]

In our case we have no desire to get historical files for particular releases at any point in time as those files I mentioned have been superseded by newer versions and are no longer relevant to us, which is why we would like to obliterate them.

Our workflow is to branch and support the previous and current release versions while working on a trunk version of the next release. What is current at the time of the release is what is supplied to customers, and we only do bug fixes to code from that point forward. Bug fixes go out as new build of that particular release, with no changes to any third-party files. Clients have to be on the latest build of a particular release in order to get support.

Obviously our work method is not what everybody does, but it does work for us.

[jclausius]

So, if you could mark a file (or a group of file) to only retain the "latest" version that would work too, correct?

[BigBrett]

Not really.

We have 40 odd DLLs with names like TD_Db_19.12_14.dll which in the next version from the supplier becomes TD_Db_20.5_14.dll, then through 20.8, 21.1, 22.1, 22.2 and currently TD_Db_22.7_16.dll.

The files can't be renamed because internally the code generates a version specific filename for loading additional files.

22.7_16 is the version that will be going out with our next release, We still have deleted versions 20.8 and 21.1 in this particular release which can't be obliterated because those deleted DLLs were in previous branched versions.

[jclausius]

Ahh. Different filenames... Gotcha.

Thank you for the clarification.