I have no idea what you are talking about. The question at hand is if you still need 15.4 in Documentation:Tools. I suggest you do not. If I find that and earlier EOL releases in other projects I will request the same.
In my opinion, this should be regulated centrally and automatically across the board.
For example, all repos should be automatically deleted three months after the new version has been released.
And everywhere.
Please don't! We need these containers for our translation vendors. It's slowly migrated to newer version, but it takes some time. We need 15.4 for our container.
Deleting it would cause some service interruption.
But that has been the case for a few days now. 15.4 it's gone here.
And why do you need data from a long-dead version (since - Dec 31st 2023 -)?
There seems to me to be something wrong with the processes.
We could, but should not first delete the 15.3 in other repos?
Sure we can remove these too, but they are independent.
Unfortunately, consistency, clarity and a clear approach are once again lacking.
I have no idea what you are talking about. The question at hand is if you still need 15.4 in Documentation:Tools. I suggest you do not. If I find that and earlier EOL releases in other projects I will request the same.
In my opinion, this should be regulated centrally and automatically across the board. For example, all repos should be automatically deleted three months after the new version has been released. And everywhere.
I agree, there should be a centralized effort. This is the next best thing.
42.3 have i found, too. :-)
Please don't! We need these containers for our translation vendors. It's slowly migrated to newer version, but it takes some time. We need 15.4 for our container. Deleting it would cause some service interruption.
But that has been the case for a few days now. 15.4 it's gone here. And why do you need data from a long-dead version (since - Dec 31st 2023 -)? There seems to me to be something wrong with the processes.
Nothing wrong, but sometimes things need longer than expected. But anyway, I solved it for the time being.
Well, then the deletion was good for something after all. :-)
Hehe, yes. It served as a good reminder. ;-)
How long does it take? Is the usage of an EOL distribution known to and cleared by your leadership and security team?
I know. It's fixed now and it seems we can use the 15.6 container without interruption.