Assign release automatically by dates
Registered by
Ilya Shakhat
Non-core project have different release cycles not aligned with the core. But they should be still calculated within release boundaries. Finding commit that splits releases manually is pretty difficult and boring. The goal is to automate the process and treat the first commit after specified date as a boundary between versions.
Use case.
Project A has commits made 29 Mar, 30 Mar, 2 Apr, 4 Apr. If the release boundary is set to 1 Apr, then commit from 2 Apr should be chosen as release boundary.
Blueprint information
- Status:
- Complete
- Approver:
- Ilya Shakhat
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Ilya Shakhat
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
0.2
- Started by
- Ilya Shakhat
- Completed by
- Ilya Shakhat
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Auto assign of releases to commits is implemented
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
