[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged

[Yaniv Kaul (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29503#comment-29503 ] 

Yaniv Kaul commented on OVIRT-1295:
-----------------------------------

I think we need to see how many of those we have - and how many have CR+1 and V+1 and can go through the same process as well - on lower priority (say, on 3AM in the morning).
What about running o-s-t on the first batch?

> 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 [Administrator]
>            Assignee: infra
>
> 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 at 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
(v1000.870.5#100039)