Labels

• hotlist: devRel
• hotlist: release-blocker
• jira-sync
• merge: caretaker note

  Alert the caretaker performing the merge to check the PR for an out of normal action needed or note
• merge: fix commit message

  When the PR is merged, rewrites/fixups of the commit messages are needed
• merge: preserve commits

  When the PR is merged, a rebase and merge should be performed
• merge: squash commits

  When the PR is merged, a squash and merge should be performed
• needs: discussion

  On the agenda for team meeting to determine next steps
• needs: investigation

  Requires some digging to determine if action is needed
• needs: more info

  Reporter must clarify the issue
• needs: repro steps

  We cannot reproduce the issue with the information given
• needs: verification
• ng update DX
• P0

  Issue that causes an outage, breakage, or major function to be unusable, with no known workarounds
• P1

  Impacts a large percentage of users; if a workaround exists it is partial or overly painful
• P2

  The issue is important to a large percentage of users, with a workaround
• P3

  An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
• P4

  A relatively minor issue that is not relevant to core functions
• P5

  The team acknowledges the request but does not plan to address it, it remains open for discussion
• requires: TGP

  This PR requires a passing TGP before merging is allowed
• severity1: confusing
• severity2: inconvenient
• severity3: broken
• severity4: memory/performance
• severity5: regression
• severity6: security
• state: blocked
• state: blocked on upstream
• state: WIP
• target: feature

  This PR is targeted for a feature branch (outside of main and semver branches)