<div dir="ltr">It seems like there are two sides thus far about how to proceed: one being that we should accept and implement PUP-3, and the other being that we should tweak our current process. I’d like to propose the following solution. <div><br></div><div>For the 2.14 release, we try out one of the tweaks to our current git workflow. Namely, we turn on branch protection on Github and turn off pushing to branches for all branches except master. I think this is the simplest and most effective alternative proposed.</div><div><br></div><div>Then when 2.14 is released, we evaluate whether this tweak has solved our problem or not. If it has not, we again consider moving to the workflow outlined in PUP-3. </div><div><br></div><div>I think this is the best approach as it would allow us to try out tweaking current workflow first before redoing our entire git workflow. Thoughts?</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Jun 2, 2017 at 4:05 PM, Michael Hrivnak <span dir="ltr"><<a href="mailto:mhrivnak@redhat.com" target="_blank">mhrivnak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span class=""><br><div class="gmail_quote">On Fri, Jun 2, 2017 at 12:01 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes we should enable branch protection to prevent all pushes using that script. That is one of the main benefits that accepting this pup would allow (I think).</blockquote></div><br></span>I think doing this would be at least as beneficial in a merge-forward model as a cherry-pick model. We could enable it immediately and take full advantage of the added protection.</div><div class="gmail_extra"><br></div><div class="gmail_extra">My only question would be about the build process, and whether it includes any branch pushes that we'd need to facilitate. Obviously that's doable; it's just a detail to think through.<span class=""><br><br clear="all"><div><br></div>-- <br><div class="m_-8720951406554688533gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><span style="margin:0px!important;padding:0px!important">Michael</span> <span style="margin:0px!important;padding:0px!important">Hrivnak</span></p><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"></p><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><span style="margin:0px!important;padding:0px!important">Principal Software Engineer</span><span style="margin:0px!important;padding:0px!important">, <span style="margin:0px!important;padding:0px!important">RHCE</span></span> </span><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px"></span><br style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important">Red Hat</p></div></div>
</span></div></div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>