We have had similar discussions and the only useful solution we found is to simplify (as in further automate) the release process. Since we are not announcing any release a LTS, we believe that a fix present in any version should be present in the last patch version of any greater minor branch. (Basically anything, that pip might decide to upgrade to by accident.) We try to keep that promise.
On Mon, Apr 12, 2021 at 5:57 PM Quirin Pamp <p...@atix.de> wrote: > I need some community feedback on how to handle pulp_deb dot releases (for > Katello). > > It looks like the final version of Katello with Pulp 2 in it (3.18) is > using pulpcore 3.7. > The most recent version of pulp_deb compatible with pulpcore 3.7 is 2.9. > > As a result I will need to cherry-pick any pulp_deb changes needed for the > Katello 2to3 migration back to the 2.9 branch. > However, I don't want to do dot releases for every version between 2.9 and > the current release (too much work). > > Does this cherry-pick strategy (in effect turning pulp_deb 2.9 into a > privileged LTS type thing) strike anyone as problematic? > How are other plugins handling cherry-picks (in general and for Katello in > particular)? > > Kind regards, > Quirin Pamp (quba42) > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://listman.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-dev
