@mrm - We love your work! And it’s so great to be using a self-hosted service.
Since we care lots about the excellent software you’ve written which we receive much benefit from, I’d like to humbly make two suggestions:
- No new functionality in any 1.0 betas from now on.
- Prioritise releasing a stable 1.0.
It’s awesome to have new functionality in the betas. Makes it pretty exciting to get the betas and try out a new setting or improvement. However every change introduced adds the risk of new bugs.
I think the priority should be to ship a 1.0 release, and then use 1.1, 1.2, and so on (or whatever version numbering you’re using) for new functionality.
- Gets out of the never-ending cycle of fix-bug → introduce nifty feature → now fix new bugs.
- New users will feel more confident using a non-beta 1.0 release (and especially a 1.1 or higher version imho).
We also care about your mental well-being and would like to make sure this project remains a joy for you
Feel free to ignore / trash / trash-talk this suggestion. Much thanks for the hard work.