On 2/13/14, 1:23 PM, Honza Bambas wrote:
An optional /* @reviewer: m...@foo.com */ comment under the license would
do. If not present, find reviewer the usual way (not always hitting the
right person).
Reason is that despite we have peer lists, sometimes files are
written/maintained by non-peers of the module a file is in or should be
reviewed only by a specific peer of the module that authored or
currently maintains the file.
What is it exactly that you are trying to do?
Even if you capture this information, how does it get conveyed to the
review tool? Our current review workflow deals with diffs/patches, so
any reviewer extraction needs to be performed with full knowledge of the
repository. At that point, scanning commit history, consulting special
files (e.g. OWNERS files), or even having a script in the tree armed
with files -> reviewer knowledge all seem preferred to metadata in
individual files.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
