Hi, On Mon, Apr 15, 2024 at 11:04:22AM +0100, Ankur Sinha wrote: They are not designed to be installed in parallel, so task3 will obsolete task. However, task3 will not provide the task package, so that task will not be updated to task3 during normal upgrades. Users will have to explicitly install task3. Being a happy taskwarrior user since years: Note that users do not always update (full) OS releases, but do new installs while keeping (a.o.) /home. So, after installing that new OS release, users will face the same issue. Furthermore, if they are used to install "task", they will install the wrong version, even if they may want to use the new version. The fact that v3 does *require* a v2 for exporting is of course a bad thing, they should have added a export-v2 option or so. Will the task v3 warn users if they detect old data? What is the idea? To temporarily provide both packages, v2 and v3, that can not be installed together? About the naming / versioning part: this probably has happened before with other packages, I am not aware of all the policies. But I would think that having task2 for backwards compatibility would be a better option. Can't task2 be built in such a way that it can be installed alongside task (task v3). Cheers, -- -- Jos Vos <jos@xxxxxx> -- X/OS Experts in Open Systems BV | Office: +31 20 6938364 -- Amsterdam, The Netherlands | Mobile: +31 6 26216181 -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
