3 ms·
Author here. Thank you. :) One thing I am going to do in my new project is catalog all bugs fixed after first release with the following data points: * Is it
by gavinhoward 3y ago
Author here.
Thank you. :)
One thing I am going to do in my new project is catalog all bugs fixed after first release with the following data points:
* Is it a C bug?
* Is it in a stable module of the monorepo? (I will mark things stable after they have been tested.)
* Is the bug in a release, even if it's in an unstable module?
* Is it a build bug?
* Is it a test bug?
* Etc.
I'll keep the catalog in a human- and machine-readable format. This should provide a good set of data.
I would be thrilled if people downloaded my code for human study, analysis, and code archeology.
- pushfoo 3y agoDo you have an interface in mind to reduce friction for building the catalog on a daily basis? GitHub and Gitea don't really seem to provide clean ways to do this out of the box.
- gavinhoward 3y agoI am going to do it by hand for the first while. Until I build my VCS, which will be like Fossil and have an integrated issue tracker that gets cloned with the repo. Then I'll put the catalog into my VCS by hand and track issues normally; the catalog will build itself as people report bugs.