Most repositories stuck on Taskwarrior v2

[hunterjackson]

https://repology.org/project/taskwarrior/versions

[ryneeverett]

Perhaps a valid point, but I'm not sure looking at the sea of red on repology is a good way to gauge progress. It seems like most packages are mostly red like that. And judging by the number still on 2.5.x I wonder if they're too stable to upgrade?

[djmitche]

Good point. Also, there was a long pause after 2.6.2 so perhaps some of the folks who were maintaining those packages for those distros have moved on to other things, and never spotted the subsequent releases.

@hunterjackson if there's a specific repo/distro you would like to see upgrade, please follow that distro's process to get the update started!

I would like to have people associated with Taskwarrior who know the maintainers for each of the major distros, and can act as liasons -- helping us solve problems they encounter while packaging, and helping them know when to package a new release. Would you be interested in starting such a group?

[stefan-sherwood]

It's at 2.6.2 in Debian bookworm.

It would be prudent to add explicit release notes warning people that there are breaking changes in 3.x, specifically regarding the sync server, before they confirm via apt installation.

[djmitche]

It would be prudent to add explicit release notes warning people that there are breaking changes in 3.x, specifically regarding the sync server, before they confirm via apt installation.

Do you mean in the Debian release notes? If so, that's a suggestion for the Debian packagers, not the TW devs! If not -- that already exists.

[stefan-sherwood]

I don't know what it's called but when someone updates their packages via apt-get (e.g. apt-get update; apt-get upgrade) some packages require you to read their blurb before you upgrade. They often do this when there are breaking changes, legal changes, or other considerations the user should know about before upgrading.

Sorry, I don't know who does what. I'm just pointing out that a lot of people routinely upgrade their packages without looking at the release notes because they can usually assume there are no major breaking changes without a warning. Of course with millions of developers there are exceptions (pun intended).

[djmitche]

Oh, interesting, I've never seen that on my Ubuntu systems!

[cameronj86]

Debian stable is still on 2.62 as expected, but I do want to point out that testing and unstable are also still on on 2.62 as well. The freeze for Debian 13 goes into effect on 3/15.

If getting v3 in Debian 13 is a possibility, it would streamline the upgrade process given the # downstream distros.