Package: taskwarrior Version: 2.6.2+dfsg-1 Severity: wishlist X-Debbugs-Cc: tj.iam...@proton.me
Since v3.0 was recently released I expect there will be a move to it at some point. I'd like to request keeping v2.x and v3.x in parallel for the following reasons (or at least until they are no longer significant): v3.x has a LOT of regression bugs v3.x has removed many features v3.x has replaced the data(base) storage v3.x has completely removed taskd server The last issue in particular is problematic since the suggested workaround is to host the (new) sqlite database in "Cloud Storage" that, currently, only is Google Cloud Platform. The 'local' option is shared directory (which infers NFS/CIFS/sshfs and similar) for local networked instances whereas v2.x taskd uses internal TLS. Using TaskChampion's replacement for taskd TLS means one has to nominate one client as the 'master' to avoid recurrence sync/duplication bugs. It seems like the move to TaskChampion store/sync engine was premature since it is "currently best described as a reference implementation of the Taskchampion sync protocol." https://github.com/GothenburgBitFactory/taskchampion-sync-server/blob/main/README.md
