We need to agree on an Archiving policy for MLDS, now that we have archiving functionality in the system (rather than just delete)
I would like to preferably move to an N-2 policy, however would that would for everyone wrt International Edition releases? (eg)
Would you be happy just to have say the following releases available in the MAIN folder:
-
April 2025
-
May 2025
-
June 2025
Or, do you consider the previous Jan/July releases to also be “current” (as opposed to “archived”)? So it would then look like this in the main folder:
-
July 2024
-
January 2025
-
April 2025
-
May 2025
-
June 2025
Note: The current Archiving functionality only allows the SI Release Team to move packages back and forth from the main to the archived repos. This would mean if you wanted an older package you’d have to raise a ticket for us to put the package back in the main repo.
Whilst this may sound onerous at first, it’s actually useful for more than just efficiency purposes - it also forces uses to consider whether or not they actually need an older (potentially clinically unsafe) package, or if they should actually be using a more recent one.
Is this archiving policy acceptable? Or does it require refinement?