Hmmm. Your link distinguishes 3 cases, out-of-tree (such as
in a github bug tracker), off-branch (which appears to be what
you are suggesting, right?), and on-branch (part of the sources
in the Axiom scheme).
He raises the question of merging bugs where systems might
have custom software to do thi
On 08/06/2016 01:28 PM, Tim Daly wrote:
> Methinks I mis-understood your DAG suggestion.
>
> Are you suggesting that the source code is in one DAG
> (src/doc/build/etc) and that bugs are in a parallel DAG?
More or less yes. I think it is a bit like when you document a project
on github.
https://
Methinks I mis-understood your DAG suggestion.
Are you suggesting that the source code is in one DAG
(src/doc/build/etc) and that bugs are in a parallel DAG?
Are you also suggesting that the "bug DAG" be a git repo
separate from the source repo?
In a pile-of-sand (POS) project organized by a dir
On 08/06/2016 02:51 AM, Tim Daly wrote:
> Fixed bugs seem uninteresting. Several things failed on my car, for
> instance, that were fixed. There is rarely the need to revisit
> failures, except possibly in regression tests, like brakes :-)
I don't understand your comment. You are in favour of ev
Fixed bugs seem uninteresting. Several things failed on my
car, for instance, that were fixed. There is rarely the need
to revisit failures, except possibly in regression tests, like
brakes :-)
Except for release notes, why would anyone want to know about
fixed bugs? At most someone running an old
> 6) Bugs are part of the source tree
To me, it would be sufficient, if fixed bug come with a commit message
that describes the bug that is fixed and the source code contains a test
that corresponds to the bug.
I don't necessarily need open bugs in the source tree. They could live
in the same rep
The bug list brings out several aspects of literate programming
that are not obvious at first glance but make a qualitative
difference in maintaining code. Previously people have turned
to IDEs to provide these features. IDEs are just more code to
maintain, often with very task-specific hacks that
