Scott Gray wrote: > On 23/03/2010, at 9:46 PM, Adam Heath wrote: > >> Scott Gray wrote: >>> On 23/03/2010, at 9:37 PM, Adam Heath wrote: >>> >>>> Scott Gray wrote: >>>>> This seems important, could you explain how it works a little more? >>>> There was a thread about this recently, where I announced which >>>> classes had full coverage. This annotation just means that the >>>> person(s) listed in the annotation are monitoring the source. That >>>> means that those people might be who to turn too if there are >>>> questions on how the code works. >>> But what does it do functionally? How would it be different from: >>> // "Don't mess up my code buddy!" signed Adam Heath >> Shows up in javadoc. > > Got it > >> The retention policy could be changed to to Runtime, so that a test >> case that fails could report something automatically. > > Doesn't buildbot do that for us already?
The person who breaks the build is different then the person who might know a bit more about the code in question. >> Remember, annotations are easier to access programatically. > > My only concern is that we removed all author information when we moved to > Apache and this feels very similar to it. I understand you're not claiming > authorship but it does feel kind of implied. Good point. But, this isn't an author tag. Author tags imply that they will grow without bound, for everyone who ever modifies something, would need to add their author tag.
