[
https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jir...
]
eyal edri commented on OVIRT-1295:
----------------------------------
[~tnisan(a)redhat.com] is this still needed? I didn't see any issues during 4.2
development which required an additional flow other than existing change queue.
If so, can you elaborate more on the need, maybe as a user story so we'll understand
the problem at hand.
Add job to auto-rebase patches that are ready to be merged
-----------------------------------------------------------
Key: OVIRT-1295
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1295
Project: oVirt - virtualization made easy
Issue Type: Improvement
Reporter: eyal edri
Assignee: infra
Priority: Low
We want to help stable branch maintainers to minimize the time needed for merging
approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge
conflicts.
A suggestion was made to create a job which will detect patches ready to be merged with
the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to
submit a patch, hopefully the patch won't need a rebase and can be merged without
further waiting for rebase or CI.
This approach might introduce challenges when working on patches that are dependent on
other patches and a specific logic might be required to handle special cases.
[~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement,
please comment or add thoughts if I missed anything.
Initially we'll try enabling it for ovirt-engine on 4.1 branch.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)