Re: Capturing additional metadata in moz.build files

2015-02-17 Thread Gregory Szorc
I'm starting to work on this implementation. https://reviewboard.mozilla.org/r/3817/ Feel free to comment on the diffs. https://reviewboard.mozilla.org/r/3935/diff/#0 is where it starts to get interesting. On Tue, Dec 9, 2014 at 10:46 AM, Gregory Szorc wrote: > In Portland, there were a number

Re: Capturing additional metadata in moz.build files

2015-01-22 Thread David Burns
The last bullet for me is the killer feature. I recently hit an issue where I made some fairly big change to an API and updated all the consumers that I was aware and even ran a try push for the "happy" set. Unfortunately this burnt the tree. I see this situation as a bigger waste of resources (sh

Re: Capturing additional metadata in moz.build files

2014-12-10 Thread Gregory Szorc
On 12/10/14 9:48 AM, Ehsan Akhgari wrote: On 2014-12-10 12:30 PM, Benoit Girard wrote: On Tue, Dec 9, 2014 at 1:46 PM, Gregory Szorc wrote: * Building a subscription service for watching code and reviews They all sound great. Except I'm not sure what you mean by this one. Are you suggesti

Re: Capturing additional metadata in moz.build files

2014-12-10 Thread Philipp Kewisch
On 12/9/14 7:46 PM, Gregory Szorc wrote: > * Building a subscription service for watching code and reviews I think this would be quite interesting, but I'm also not quite sure what metadata you would put into the files. In the past I've built a small script that uses mozilla pulse to figure out w

Re: Capturing additional metadata in moz.build files

2014-12-10 Thread Ehsan Akhgari
On 2014-12-10 12:30 PM, Benoit Girard wrote: On Tue, Dec 9, 2014 at 1:46 PM, Gregory Szorc wrote: * Building a subscription service for watching code and reviews They all sound great. Except I'm not sure what you mean by this one. Are you suggesting that we have something like a list of em

Re: Capturing additional metadata in moz.build files

2014-12-10 Thread Benoit Girard
On Tue, Dec 9, 2014 at 1:46 PM, Gregory Szorc wrote: > * Building a subscription service for watching code and reviews > They all sound great. Except I'm not sure what you mean by this one. Are you suggesting that we have something like a list of email in moz.build to register for updates to a

Re: Capturing additional metadata in moz.build files

2014-12-09 Thread Nicholas Nethercote
On Tue, Dec 9, 2014 at 10:46 AM, Gregory Szorc wrote: > > I discussed options with Mike Hommey and we believe that moz.build files are > the appropriate default location for this metadata. We considered > alternatives such as moz.build-like Python sandboxes under a different > filename and standal

Capturing additional metadata in moz.build files

2014-12-09 Thread Gregory Szorc
In Portland, there were a number of discussions around ideas and features that could be easier implemented if only we had better metadata and annotations for source files. For example: * Suggested reviewers for a patch * Determine the Bugzilla component for a failing test * Determine the Bugzil