sanitizers / sanitizers/patchback-github-app

[TODO] Implement backporting policy configuration

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
14
Forks
10
Avg merge
4m
Merged PRs (30d)
3

Description

What I have in mind is having a config structure that would allow the repo to say that the current version is X and the policy for bugfixes is X-1, the policy for security fixes is X-2 (for example).

Then, it'd allow us to implement the flow where having a bug label would trigger backports to the previous version and having security would trigger backports to two previous versions. Alternatively, this could be made explicit with needs_bug_backport / needs_security_backport (via opt-in or opt-out).

The last bit needed is to allow the repo to specify what part of the version spec to consider a bump (whether for v2.1.1 X-1 is considered v1.0.0, or v2.0.0, or v2.1.0).

Depends on: https://github.com/sanitizers/patchback-github-app/issues/5
Depends on: https://github.com/sanitizers/patchback-github-app/issues/6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading dependent issues #5 and #6, then inspect the repository's existing configuration and backporting entry points. Define how version levels, bug and security labels or opt-in flags, and bump semantics should be represented before implementation. Done means a repository can configure these policies and the backport flow applies them consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python
Domain
devops, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.