https://bugzilla.redhat.com/show_bug.cgi?id=1902024 --- Comment #4 from code@xxxxxxxxxxxxxxxxxx --- > I think there are pros and cons to that. Yes, I agree. In the end, the EPEL versions are separate branches in Pagure either way; they may or may not have the same contents as the Fedora branches. The question is whether to handle the divergence in spec file syntax and so on with conditionals, or at the point of merging changes from Fedora master. I’ve seen both practices “in the wild.” I think I’m starting to believe in the latter. > I also haven't found any information on whether it's allowed or not to let Fedora and EPEL git trees diverge on purpose. I think this follows from the EPEL updates policy (https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies); Fedora Rawhide always wants the latest version of everything, while packages in EPEL are expected to avoid disruptive updates over the release lifecycle of as much as a decade. Divergence over time is thus guaranteed in almost all cases on the basis of differing package versions alone. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
