Project

General

Profile

Actions
Copy link

Bug #21517

open

Make rudder-dev aware of branches next for plugin

Added by François ARMAND 10 months ago. Updated 10 months ago.

Status:
Pending release
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Rudder dev tools
Target version:
master
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Regression:

Description

For plugin, the lifecycle is very complicated.
We have `7.1-next` that is the branch for rudder SNAPSHOT version.
Most dev happen in these branch.
Rudder dev does not know about them, so it tries to open PR or merge them in the standard `branches/rudder/7.1` branch.

Here, we want to at least provide a correct experience for:
- starting work on an issue (ie: rudder-dev 14345 should branch from origin/7.1-next if 14345 targets branche 7.1-next)
- commit
- merge by hand

Automatic merge may not work - it's ok, we don't want to keep that archi of branches on plugins.

Actions
Copy link
 #1

Updated by François ARMAND 10 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions
Copy link
 #2

Updated by François ARMAND 10 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-tools/pull/728
Actions
Copy link
 #3

Updated by Anonymous 10 months ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link

Also available in: Atom PDF