I do not get why it would work in that case. I assume the scenario is someone with a bike coming, doing theft, then leaving with the same bike.

Therefore there will be a period without bike, then a period with bike, then a period without bike again.

Let’s assume there is no bike on the particular moment viewed. How do you know whether it occured before or after the theft? If you make the wrong decision, you get stuck on an endless binary search… Unless you take note at each timestamp where you made the decision, draw a tree of timestamps, and go back the tree if your search is fruitless but that’s much more complicated than what this post says.

Do you happen to know where those json files are located? I have been looking for those

I love that software. It’s so simple - no need for much clicking you can do a lot with just the keyboard.

I love particularly how there is no bloatness. Creating a new task is as simple as pressing ctrl+a (or shift+a), typing the name and pressing enter. Creating a subtask is just pressing ‘a’ on the task and type the name.

There is jira integration so I can import my jira tickets and make my own local subdivision in smaller tasks that do not need to be thoroughly described or shared. The status of the jira tickets can be updated from the app directly

There is a pomodoro plugin that works well minor some bugs (don’t ever choose “close” when prompted to skip the break or go back to work)

Wonder what did I do last week for writing a summary? Just look at the history in the app

I really love it and can only recommend it for personal planning

Those are profit driven. If they can cut cost they will. They just want the minimal effort to get customers. Also usually their app has such marketing and notoriety that most people don’t really care about changelogs.

Even if the commit message is concise, there is a difference between what the patch does on a technical level and what the end user will see as a result.

IMO the solution is to link each commit to an issue or a ticket - some high-level description of the feature the commit implements - but there still has to be someone who makes the effort of making sure each commit is linked to a ticket and who nags the devs when they forget to do so…

I would say it is this way because it takes a big effort to crunch all the patches that have been made thus far and make an easy-to-read summary out of them.

It’s not something that comes for free. You need someone on the job.

I would also add that maintaining a fork means either missing out on the new features from the fork or have a lot of trouble rebasing every now and then (the more the fork is different from upstream, the higher the cost of rebasing)