<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 05/23/2018 06:20 AM, Brian Bouterse
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAcvrTEJ_RbN=pnHXm6VO4E=V2rzV+P18D89B1eXTfOQdnMShQ@mail.gmail.com">
<div dir="ltr">
<div>It sounds like there isn't much blocking this, but does
that mean the devs should go ahead with planning and making
the branching changes?</div>
<div><br>
</div>
<div>Also I want to confirm: is the scope of this planned change
only for pulp/pulp and pulp/devel repos for now?</div>
</div>
</blockquote>
<br>
Agreed.<br>
<br>
<blockquote type="cite"
cite="mid:CAAcvrTEJ_RbN=pnHXm6VO4E=V2rzV+P18D89B1eXTfOQdnMShQ@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 22, 2018
at 10:56 AM, Patrick Creech <span dir="ltr"><<a
href="mailto:pcreech@redhat.com"
target="_blank" moz-do-not-send="true">pcreech@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex"><span
class="">On Mon, 2018-05-21 at 19:51
-0400, Dennis Kliban wrote:<br>
> We need to start planning the
creation of a "2.17-dev" branch from
the current master and merging "3.0-dev"
into "master". We would then create new
"2.Y-dev" branch after each "2.Y.0"
release. All<br>
> 3.0 work would then land on
master. <br>
<br>
</span>Might I suggest a y-version
agnostic 2-dev or 2-master or similar
branch instead? This would reflect better
the state of the branch as "Pulp 2 master"
and will prevent us from having to rename
a lot<br>
of items each release. <br>
</blockquote>
<div>+1 to this naming.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
+1<br>
<blockquote type="cite"
cite="mid:CAAcvrTEJ_RbN=pnHXm6VO4E=V2rzV+P18D89B1eXTfOQdnMShQ@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<div> <br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<br>
This would also help enforce our
cherry-pick model of 'merge to master,
pick back to -release branches for
releases' and will provide us a feature
branch to branch off our '2.y-release'
branches<br>
without adding in confusion each .y cycle.<br>
<span class=""><br>
<br>
> Do our release engineering tools
support this change? If not, what would
it take to support it?<br>
<br>
</span>Yes. There'd be some small changes
required to use the new master branch
insted of 'master', but that's it.<br>
<br>
> ______________________________<wbr>_________________<br>
> Pulp-dev mailing list<br>
> <a href="mailto:Pulp-dev@redhat.com"
moz-do-not-send="true">Pulp-dev@redhat.com</a><br>
> <a
href="https://www.redhat.com/mailman/listinfo/pulp-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com"
moz-do-not-send="true">Pulp-dev@redhat.com</a><br>
<a
href="https://www.redhat.com/mailman/listinfo/pulp-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Pulp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev">https://www.redhat.com/mailman/listinfo/pulp-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>