I recently posted an RFC for maintaining Django LTS in Fedora and EPEL, and @kevin noted that the EPEL steering committee should probably vet it and it should be documented.
So here it is - https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/UR22KFETSJNXY6BNSKAQIDRDRQ5HMNUG/
(given most of the concerns are around EPEL, would it make sense to document it somewhere in the EPEL docs instead? Do we already have such a space set up?)
related, so let's not waste two issues - we need python-asgiref >= 3.6.0 in epel9 to get python-django4.2 branched, and this is sort-of an incompatible upgrade (there is a documented breaking change, but it's unclear if it even affects the two dependent EPEL packages at all)
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/62BSXONMCUCYAJ5O72G4IXU77N4ZZW3T/
https://copr.fedorainfracloud.org/coprs/salimma/asgiref-3.7/packages/
I'd like to check if I can start building updates after the meeting, or we should wait a full week per the incompatible policy - which means only one extra day anyway in this case.
will put up a draft PR to get the discussed policies added as a subpage to https://docs.fedoraproject.org/en-US/epel/epel-policy-updates/
Login to comment on this ticket.