End of Life and Archive Policy

End of Life

If a version of your project is no longer supported upstream, please mark it EoL (end of life) in VAT.

To do this, browse to your project in VAT and ensure that the master branch and the correct version are selected, then click on the project status menu on the upper right (it will probably currently be set to Active) and choose EoL. When this is done, that version of the project will show as EOL on the Iron Bank main page.

Note

We will also EoL applications and containers that are EoL upstream or that haven't been contributed to in a long time and/or have gone stale. This process and criteria are described below.

All of the following conditions will make a container or application in Iron Bank be considered EoL automatically and we will invoke the archival process, without any further communication or permission.

Upstream application/version is no longer receiving support or has been deprecated, moved to a new project or otherwise considered EoL
Any container that has had no updates within 6 consecutive months
No consumers are using the container over the course of 6 consecutive months

Once a container has been identified as EoL, a member of the container hardening team will make an issue ticket on Gitlab for that project. If there is no response the project will be archived after 60 days.

Inactive

Inactive status is placed on project repositories that have been failing Iron Bank pipelines, projects that never began development or have not attempted an initial merge request. Timelines for each are the following

Failed pipelines that have not been addressed for 90 days
Newly onboarded repositories that have not had an intial push made within 45 days of creation

Project Repositories must go to an Inactive state prior to reaching an Abandoned state, once the Abandoned threshold has been met the Inactive status will be cleared and the repository will be set to Abandoned see below for more information.

Abandoned

Project repositories that have been marked as Abandoned will have an Archive issue opened on the project repository. Project repositories will be in Abandoned state unless pipeline is successful or communication from maintainer is received. After 14 days in Abandoned state, the repository will be archived

Failed pipelines that have not been addressed for over 180 days
Newly onboarded repositories that have not had an initial push made within 90 days of creation