Today we consider only 3 labels:

• T0-node: This PR/Issue is related to the topic “node”
• T1-runtime: This PR/Issue is related to the topic “runtime”
• T2-API: This PR/Issue is related to APIs

In the current state, this PR considers only T0 and T1 and ignores T2.

We have 4 options for now (things will ease later when we fix those issues preventing multiple labels with the same letter):

• consider T2 along with T0
• consider T2 along with T1
• consider T2 along with both T0 and T1
• ignore T2

The answer depends mostly on how T2 is used at the moment.
@the-right-joyce @bkchr what are your takes on that ?

The idea here is to stop telling node users to upgrade urgently when the high prio fix is actuallly in the runtime.
At the same time, being able to tell the right users that the runtime contains a high prio fix, will also be useful.

After further checking, I see what we miss the data for the template to properly output what we want.
We only get meta about the overall highest priority. We currently don't have the highest priority for the node or runtime only. Splitting requires more aggregration in the underlaying tooling (changelogerator) that is planned for a re-write.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/2762755

The answer depends mostly on how T2 is used at the moment.
@the-right-joyce @bkchr what are your takes on that ?

Maybe the best would be to remove T2. If not someone can explain for what it is good. So, for your use case I would ignore it.

See also https://github.com/paritytech/release-engineering/issues/165

T2 is no longer existing, we won't have the same set of labels any longer and also not the same rules, see https://github.com/paritytech/labels/pull/29/files
As off now we had the feedback that the devs would like to add multiple T*labels to their PRs/issues as it helps them to classify what the issue/PR is about, so they will also not be exclusive anymore
Priority labels are also gone, we need to think of a completely new template for the releases, not based on the sets that we currently have.