Project

Profile

Help

Task #7738

Cannot backport issues that have been released

Added by daviddavis about 1 month ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

If you try to cherrypick a commit that's been released to a release branch, the commit validation fails and also the release automation will fail.

Solution

Add support for a new tag such as backport #1234 which can be added to cherry picks.

Commit Validation

Update the commit validation to use the new tag and update any attached issue. It should also skip validating the state of any fixes/closes/etc tagged issue.

Release automation

Optimally the release automation should be able to attach the backport issues to the release milestone. Perhaps it could git blame the CHANGES entries.

If this is too difficult, another option would be to disable this part of the release automation for release branches.

History

#1 Updated by daviddavis about 1 month ago

  • Description updated (diff)

#2 Updated by daviddavis about 1 month ago

  • Description updated (diff)

#3 Updated by fao89 about 1 month ago

  • Tracker changed from Issue to Task
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

Please register to edit this issue

Also available in: Atom PDF