Andrew 👽 Yourtchenko <ayourtch@...>
My opinion hasn’t changed - it’s possibly a combination of the below two approaches:
I would suggest starting with the step (3) and the safest option to implement is the two stage process:
- moving outdated hicn project artifacts from fdio/release to fdio/attic (to be created if exists)
- deleting the hicn artifacts from fdio/atticthat were added in the previous cleanup cycle or before that.
This approach in itself is implementable in two phases, and the first phase (release=>attic) is reversible, should any glitch arise and should any unnecessary packages be archived.
Since that work will be useful to verify even after the testing, and since from experience we know we can go to bit higher quantify of packages before the wheels fall off, I would also suggest that you can use the current state of fdio/release repo as a verification that the implementation of step (3) works correctly.
We can then revisit the situation and assess whether the step (4) is even needed, or if (3) is good enough.
What do you think ?
On 6 May 2020, at 14:45, Luca Muscariello <muscariello@...> wrote: