Trail Sense Development Update (March 2026)

[kylecorry31]

In order to have more time to develop and test Trail Sense features, especially when the weather is nice, I'm going to be switching to a roughly 2 month release cycle. That's just a general guideline (always has been), so you may see more or less frequent releases.

As you may know there are a lot of feature suggestions ("Issues" in GitHub) for Trail Sense, which would take me many years to complete. I've spent a lot of time going through them and evaluating whether I actually want to implement all of them and closed the ones I don't plan to implement or support. If you provide a convincing enough argument, I may reopen some of them.

I've also gone through and tagged items as "help wanted" or "Status: Community Only". The "help wanted" label is for items that I would accept PRs for (see contributing policy) and the "community only" label is for items that I don't plan to implement but would accept PRs for. If an issue is open and does not have the "community-only" label, then it means I currently plan to implement it at some point (no timelines though). I can probably mark more as help wanted, but I'll need to provide more details to meet my architecture criteria - the ones that I would find fun to implement won't get "help wanted" though, sorry :)

I'm not sure I'm done organizing the issue backlog, so if you see something you want implemented, give it a thumbs up or follow the issue in case I close it and you think it should be implemented. Right now, Trail Sense meets pretty much all of my use cases, so as I think more about some of the issues expect more to move into the community only category or get closed out.