It's getting hot in the oven! We are down to 4 open issues in our 2.6.0 release milestone. Expect a new release soon 🙂
As Taskwarrior is firmly entering it's teenage years, it's more important than ever that it takes care of its looks. That's why our README recently got a facelift:
Ensuring high performance is on the top of our minds. Recently we fixed important performance bottlenecks, resulting in several-fold increase in execution speed.
Despite new features, our 3.0 (June 2021) release is shaping up to be the fastest TW release ever.
This is made possible by having two separate config variables for the context, the "context.<name>.read" and "context.<name>.write". The legacy option of "context.<name>=<filter>" is still supported, but it cannot distinguish between read and write operations.
The task ID 4 gets "project:Work" (the definition of the "work" context applied automatically.
For contexts with more complex filters (i.e. with boolean expressions), you can define "read" and "write" subtypes separately (note the "urgent" context below):
Writeable contexts just landed on the development branch of Taskwarrior (2.6.0) today. The context now gets applied as default modifications when creating new tasks, see below:
taskwarrior.org/news/news.20…
HELLOTUX quality shirts are available. One way to donate to the project.
#hellotux #taskwarrior
Tastes better when the work is under control.
#taskwarrior @MZAWeb








![[task@warrior ~] git rev-list --count v2.5.1..v2.5.3
917
[task@warrior ~] git diff --shortstat v2.5.1..v2.5.3
560 files changed, 11761 insertions(+), 34179 deletions(-)](https://pbs.twimg.com/media/Eq3rr5yXEAExcyW.png?name=small&format=webp)



