I believe the issue tracker should be separate (API wise) but hooked in. Manipulating it outside the codebase is what people want. That doesn't mean it can't also be a distributed system, just that it should be separate from the code.
(Reducio ad absurdam: if you want the bug tracker integrated with the code, keep the bugs as text files in a subdirectory of the git repo: you can then file bugs by pull request, and update the state of the bug along with commits to the code)
Power management, mobile and firmware developer on Linux. Security developer at nvidia. Ex-biologist. Content here should not be interpreted as the opinion of my employer. Also on Mastodon and Bluesky.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: vcs with integrated issue tracker
Date: 2014-05-21 04:08 pm (UTC)(Reducio ad absurdam: if you want the bug tracker integrated with the code, keep the bugs as text files in a subdirectory of the git repo: you can then file bugs by pull request, and update the state of the bug along with commits to the code)