Thanks for doing this! In Brussels, we talked about potentially adding even more components, such as frontend and asm.js and the debugger. Regardless of whether we end up doing that nor not, I think extracting the JITs as their own component is a great change.
On Mon, Oct 7, 2013 at 4:18 PM, Jan de Mooij <[email protected]> wrote: > As previously discussed on this list, there's a new "JavaScript Engine: > JIT" component for all bugs related to Baseline, Ion and Odin. > > Please file new JIT bugs in this component. If you're not sure a bug is > JIT-related, just file it and somebody will triage and move it if needed. > Also, don't forget to update your Component Watching settings or bugzilla > queries if you're interested in these bugs :) > > The YARR regex engine has its own JIT but let's keep these bugs in > "JavaScript Engine". YARR should probably have its own component but there > aren't that many YARR bugs so for now it doesn't matter too much. > > For the existing JIT bugs, we can do a mass move of all bugs that have > IonMonkey, OdinMonkey etc in their title. This will trigger a ton of > bugmail though so we probably want to wait a few days until everybody has > caught up with their summit bugmail. We can also just leave them in the JS > component and move only the active bugs. Any suggestions will be > appreciated. > > Cheers, > Jan > _______________________________________________ > dev-tech-js-engine-internals mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
