Code review and coverage marks

anatoly techtonik techtonik at gmail.com
Mon Aug 4 08:47:14 EDT 2014


On Sun, Aug 3, 2014 at 7:52 PM, anatoly techtonik <techtonik at gmail.com> wrote:
> On Sun, Aug 3, 2014 at 7:25 PM, Matthew Turk <matthewturk at gmail.com> wrote:
>> On Sun, Aug 3, 2014 at 11:23 AM, Mads Kiilerich <mads at kiilerich.com> wrote:
>>>
>>>> Is there a capability in Kallithea to store personal labels attached
>>>> to source code lines, such as code coverage marks and review
>>>> coverage with comments? Basically I need to label reviewed lines
>>>> in some product as I do security research, so that I knew that
>>>> these lines there reviewed by me (or smb. else) at a certain date.
>>>>
>>>> Is that possible with Kallithea?
>>>
>>>
>>> No. How should that work when files are changed?
>>
>>
>> (Speculating) They could be tied to a given file line and managed in the
>> same way as, say, "hg annotate" works?  So comments would be tied to line &
>> changeset, and then whenever the line is changed it would be "dirty" and the
>> comment would be invalid?
>
> Right. Application-specific annotations. Not only for comments, but for any
> type of content. For example, code reviews will need effective storage to get
> all reviews by all people for a give line. Also, code coverage may need filters
> from different buildbots.

One of the application areas of such review/mark/tag system is to track
changes in laws.


More information about the kallithea-general mailing list