Redmine is a solution to all the features you ask for. It is open source can be run out of a Docker container, onsite, for a 'free' option.

I see :cool:

Yes I do know what you mean. But the point is consumers of your library will not know (or really care?) about the history of the code, they just want to use code that works and is good quality. If perhaps you change the wording and asked if consumers would like un-optimised code or broken code, neither sound all that appealing. :-D

1. Optimised code that does not work is not optimised code.. it's broken code. 2. Get on and fix it - use a good LA to look at timing and data value differences on the bus of when it works/compared to not working. 3. Do not release known broken code. 4. Consider people asking to use DMA....

Doubling battery life? What (sorcery) tablet is this?