Project status update

[swellweb]

Small update from my side.

TargetBridge is not abandoned, but development will probably move a bit more slowly for a while because I need to balance it with other work and the time I can realistically dedicate to it.

I’ll still keep an eye on important issues, regressions, and community PRs when I can, but for the moment new features and non-urgent fixes may take longer than usual.

I also want to say clearly that I really appreciate all the help the project has received so far. Bug reports, testing, ideas, feedback, and code contributions have all helped TargetBridge move forward in a very real way.

For anyone who would also like to support the project financially, GitHub Sponsors is available, and that genuinely helps make it easier for me to justify spending time on maintenance and future updates. That said, community help in the form of testing, feedback, and pull requests remains extremely valuable and very much appreciated.

[swellweb]

Just to be clear: financial support is completely optional.

If you prefer to help by testing, reporting regressions, improving docs, or opening PRs, that is still hugely valuable to the project and very much appreciated.

[ThomasWaldmann]

Thanks for the quick paced releases in the initial phase!

Maybe a more relaxed way to deal with branching and releases would be:

• do bugfix releases from a maintenance branch, e.g. 3.1-maint branch is created from 3.1.0 release and can then be used to create 3.1.1, 3.1.2
• bigger features are developed in main branch and can then lead to a 3.2.0 release at some time (and a 3.2-maint branch)
• bug fixes are usually done in main and cherry-picked into the maint branches

That way, releases can be stabilised and fixed easily without bigger release development blocking a fix release. No time pressure to get big stuff done just because fixes also need to get released.

[swellweb]

Thanks, this is a very good suggestion.

I like this release model a lot, especially the idea of keeping main for ongoing feature work and using dedicated maintenance branches for bugfix releases like 3.1.1, 3.1.2, and so on.

It feels like a much healthier way to keep releases stable without creating pressure to bundle bigger changes just because a fix also needs to go out.

I appreciate you taking the time to write it out so clearly.