On Mon, Apr 15, 2024 14:18:59 +0200, Jos Vos wrote: > On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote: > > Hrm, but the problem here is that a user that currently has the task > package installed (currently v2) will end up with v3 if I update the > task package to v3---which is something we'd like to avoid here. > > Just a side question: is this task v3 update planned to be distributed > *during* an OS lifecycle or only at the start of a new one (e.g. F41, > I assume it is too late for F40 now)? Are there any Fedora policies > for this kind of incompatible updates?
The general policy is to not introduce backwards incompatible changes to stable releases: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases I am thinking that the best way for this would be to announce it as a self-contained change so it'll land in rawhide (F41). In the meantime, I can perhaps keep a COPR repository for stable Fedora releases (F39/F40) for users that do want to use taskv3 already. https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_self_contained_changes How does that sound? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
