<div dir="ltr">In RPM plugin we use it quite happily. <div>I guess it depends on the scale and the amount of PRs which might be problematic and create conflicts.</div><div><br></div><div>I'm ok to cherry-pick manually, if it's decided for the cherry-pick processor to be retired. The load is not high at the moment.</div><div><br></div><div>Tanya</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 10, 2020 at 9:24 PM Robin Chan <<a href="mailto:rchan@redhat.com">rchan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I can't speak to the work delta between the existing processor and doing them manually, but maybe we can initiate a conversation about this and other challenges with cherry picking and building with the build team?<div><br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-family:RedHatText,sans-serif">
Robin Chan<span style="color:rgb(170,170,170);margin:0px;font-size:14px"></span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;text-transform:capitalize;font-family:RedHatText,sans-serif">She/Her/Hers</p>
<p style="font-weight:normal;margin:0px;font-family:RedHatText,sans-serif">
<span>Satellite Software Engineering Manager - Pulp</span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;font-family:RedHatText,sans-serif">
<a style="color:rgb(0,136,206);margin:0px;text-decoration:none;font-family:RedHatText,sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span></span></a>
</p>
<div style="margin-bottom:4px">
</div>
<p style="font-weight:normal;margin:0px;font-family:RedHatText,sans-serif">
IRC: rchan
</p><p style="margin:0px;font-family:RedHatText,sans-serif"><span style="color:rgb(0,0,0);font-family:Overpass,"Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif">Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.</span><span style="font-weight:normal;font-size:12px"><span><br></span></span></p>
<div style="margin-top:12px">
<table border="0">
<tbody><tr>
<td width="100px"><a href="https://www.redhat.com" target="_blank"> <img src="https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png" width="90" height="auto"></a> </td>
</tr>
</tbody></table>
</div>
</div><div><br></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 10, 2020 at 2:48 PM Brian Bouterse <<a href="mailto:bmbouter@redhat.com" target="_blank">bmbouter@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 10, 2020 at 1:34 PM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">As creator of the cherry pick processor, I'd like to propose we ditch it. It requires a lot of upkeep which doesn't really save us time over just doing the cherry picks ourselves. Also, it often fails because it cannot make intelligent decisions when there are merge conflicts.<div><br></div><div>Instead what I'd propose is that we do cherry picks at release time. We do z-releases infrequently and they are usually for a particular stakeholder so we usually know which issues the stakeholder needs and can cherry pick these changes ourselves before we do a release. We can also continue using the "Needs Cherry Pick" labels to help us remember issues we want to include in a z-release later on.</div><div><br></div><div>Overall, I think disabling it is the best path forward but I'm also interested in any feedback people may have to improve the cherry pick processor. </div></div></blockquote><div>I agree with you. Also if we do keep something like this we probably should use one that is already made, e.g. gerritt. <a href="https://www.gerritcodereview.com/" target="_blank">https://www.gerritcodereview.com/</a> +1 to for now retiring it.</div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>David</div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>