Dynamic release cycle for UMD Peter Solagna EGI

Dynamic release cycle for UMD Peter Solagna – EGI. eu

Problems to solve • After the end of EMI there won’t be coordinated releases: PT will release when they wish, where they wish • There will be urgent releases also in the future bug/vulnerabilities

Proposal for dynamic UMD releases For every repository group (every high level repository structure we will have) • Stable repository • Update repository • Products, when successfully tested in verification & staged rollout are pushed in the update repository – No integration tests, no coordinated release of multiple products. – Sites will know that the products in that repository have been tested in SR, and successfully

Proposal for dynamic UMD releases pt 2 • Every three month products from the update repository are rolled into the stable repository – A policy to qualify products to be released in the stable should be discussed • In the stable repository products are released with “official” coordinated releases – New dependencies are tested to be safe for the other products in the stable repository • To keep the stable repository safe from the EPEL updates, products must be fetched with all their dependencies. Nothing should be able to alter the product in the stable repositories

Advantages • The release of a new product in UMD (update repository) is depending only on the will of EA to process quickly the staged rollout • Sites who are not interested in the latest updates can use only the stable repo, without risking dependencies issues, which are possible in the update