Announcing Jansa Branch

Hello All Developers,

The Jansa branch has been created from master for all repos!

From this point on, EVERYTHING destined for Jansa MUST be labeled with jansa/yes? and will follow the new backport process described here.

jansa/yes? – request to be considered for backporting during triage meeting.

jansa/yes – approved for backport by triage team to be included in next build of Jansa

jansa/no OR no jansa label – upstream master-only targeting K-release

If a cherry-pick has conflicts, @simaishi will post the results in the PR and add the label jansa/conflict , meaning the original developer needs to create a PR on the jansa branch with the conflict resolved. The following rules apply for backporting a PR:

  • title will be automatically prefixed with [JANSA] by the bot
  • have a link to the PR on master
  • assigned to @simaishi
  • have same labels as PR on master

Should you have any questions or comments, please do not hesitate to contact @dmetzger, @simaishi, @chessbyte, or @Fryguy.