Am Donnerstag, dem 02.11.2023 um 07:14 -0700 schrieb Jay Faulkner:
A stable release is usually as basic as a single commit patch to the releases team repo that their automation usually makes trivial. Is there something about kolla-ansible which makes releases more difficult? Or just trying not to add another item to the todo list, no matter how small?
Just curious!
I think it's the latter, as the process is even documented here: https://docs.openstack.org/kolla/latest/contributor/release-management.html#... although the branch names are currently out of date there. On the plus side, I was contacted off list by a volunteer who want's to help in that area, so maybe we can soon see the return of stable releases to pip. the nature of our integration project still is, that many integrated third party software projects tend to break rather often in various new and exiting ways. Most of the time these are fixed rather quick in git. But even if we would have monthly stable releases with all fixes - and all backports merged, which is another issue due to core reviewer capacity - it's possible you have to wait 4 weeks or even more until a fix hits pypi.org. I guess for most of the experienced users it's just simpler to install via the git source branch. after all pypi is just that git branch with extra steps, imho. Are there any other projects out there that maybe have automated this kind of release management in CI already (proposing patches to the release repo)? -- Sven Kieske Senior Cloud Engineer Mail: kieske@osism.tech Web: https://osism.tech OSISM GmbH Teckstraße 62 / 70190 Stuttgart / Deutschland Geschäftsführer: Christian Berendt Unternehmenssitz: Stuttgart Amtsgericht: Stuttgart, HRB 756139