Actions
Bug #21517
closed
Make rudder-dev aware of branches next for plugin
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
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.
Updated by François ARMAND almost 2 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND almost 2 years 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
Updated by Anonymous almost 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-tools|08b7f3578973e7c368a87249e45d8c28b1629e1b.
Updated by Vincent MEMBRÉ about 1 month ago
- Status changed from Pending release to Released
Actions