Skip to content

Improve the componentspecific model to use information from the component model #5893

@marco-c

Description

@marco-c

The componentspecific model currently just takes as input the data from the bug and decides whether it should be moved out of Firefox:General or not.

A better approach would be to add the output of the component model as features (maybe the top-3 choices):

  • top1 choice = Firefox::Component 1
  • top1 score = 0.8
  • top2 choice = Core::Component 2
  • top2 score = 0.15
  • top3 choice = Core::Component 7
  • top3 score = 0.05

Then use the following as labels:

  • keep in general
  • use top1
  • use top2
  • use top3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions