Skip to content

update pull request template with target branch guidelines#11861

Draft
slawekjaranowski wants to merge 1 commit intoapache:masterfrom
slawekjaranowski:pr-template-branches
Draft

update pull request template with target branch guidelines#11861
slawekjaranowski wants to merge 1 commit intoapache:masterfrom
slawekjaranowski:pr-template-branches

Conversation

@slawekjaranowski
Copy link
Copy Markdown
Member

What changed:

  • Added a comment section specifying accepted target branches.
  • Clarified the purpose of each target branch in the template.

Why:

  • To provide clear guidance for contributors on where to direct their pull requests.
  • To streamline the contribution process and reduce confusion regarding branch usage.

What changed:
- Added a comment section specifying accepted target branches.
- Clarified the purpose of each target branch in the template.

Why:
- To provide clear guidance for contributors on where to direct their pull requests.
- To streamline the contribution process and reduce confusion regarding branch usage.
@slawekjaranowski slawekjaranowski self-assigned this Mar 28, 2026
@cstamas
Copy link
Copy Markdown
Member

cstamas commented Mar 28, 2026

I would form "pairs":

  • master + maven-4.0.x => users should create PRs against master only, and signal us if they want it backported (we want to keep them in sync as much as possible)
  • maven-3.10.x + maven-3.9.x => users should create PRs against maven-3.10.x but signal if they think their PR fixes a bug that must be backported to 3.9.x as well (and we triage it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants