<div dir="ltr">Since this is a change from Pulp 2, I think it would be helpful to outline the reasoning behind such a change and ask that spell those out here for transparency. In addition, are there any concerns we think others may have or new problems that such a change brings about that we need to work to answer?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 17, 2018 at 11:57 AM, Dennis Kliban <span dir="ltr"><<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@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"><div class="gmail_quote"><span class="">On Tue, Apr 17, 2018 at 11:50 AM, Eric Helms <span dir="ltr"><<a href="mailto:ehelms@redhat.com" target="_blank">ehelms@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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Apr 13, 2018 at 4:40 PM, Dennis Kliban <span dir="ltr"><<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@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><div class="gmail_extra"><div class="gmail_quote"><span>On Fri, Apr 13, 2018 at 1:25 PM, Patrick Creech <span dir="ltr"><<a href="mailto:pcreech@redhat.com" target="_blank">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">Pulp,<br> <br> So, while working on the packaging work, I figured it be nice to start talking about release process expectations around nightlies, beta, and GA.<br> <br> Generally, what is pulp's release plan? What are the expectations here?<br> <br></blockquote></span><div><br>The release process for Pulp 3 will be different from what we do for Pulp 2. Our plan for publishing Pulp 3 with quality to PyPI is outlined on our wiki[0]. We are hoping to be able to release to PyPI once a week during the beta cycle. After the packages are published to PyPI, any of the derivative packaging (RPM, Debian, etc) can be performed. The build team can decide how often the derivative packages need to be produced. <br></div></div></div></div></div></blockquote><div><br></div></span><div>This implies that, for the Pulp developer team, Pypi is considered the release vector and that derivative release vectors (e.g. RPM, Deb, etc.) are considered community contributions that are not part of the core release process. Is that a fair summary of the position? Consumers of non-pypi release vectors will need to assume a delay between announced release and RPM release. Which then, unlike Pulp 2, means the team handling RPM for example would manage build and release announcement on our own schedule. I want to clarify so that we set expectations for developers and users and so that we can set our expectations for how we shift compared to Pulp 2.</div><div><br></div></div></div></div></blockquote><div><br></div></span><div>You are correct in your understanding. <br></div><span class=""><div> </div><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"><div class="gmail_quote"><div></div><div>If the above is the agreed workflow (and change for Pulp 3) I think the rest of the questions I'd ask related to the points below are answered and we can talk a bit further on these points above.</div><span class="m_3211303209655173799HOEnZb"><font color="#888888"><div><br></div><div>- Eric</div></font></span><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div><br>[0] <a href="https://pulp.plan.io/projects/pulp/wiki/Continuous_Delivery_of_Pulp_3" target="_blank">https://pulp.plan.io/projects/<wbr>pulp/wiki/Continuous_Delivery_<wbr>of_Pulp_3</a> <br> </div><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> And also, more specifically,<br> <br> Based on what we do for pulp 2, when will pulp 'code freeze'? What is the expected turnaround from 'code freeze to 'packages shipped'. We should probably agree on some expectations of turnaround<br> time.<br> <br></blockquote><div><br></div></span><div>The code will be frozen when it is published to PyPI.<br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Is there a staging process in place yet for packages (pypi or rpm)? Is there testing expectations of these pre-release bits to ensure quality? With pypi being a valid install location, are these<br> releases to be coordinated? <br> <br></blockquote><div><br></div></span><div>As outlined on the wiki, we plan to ensure quality at merge time of every commit.<br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Where are pulp 3 bits expected to be hosted? How are we going to handle signing packages?<br></blockquote><div><br></div></span><div>Pulp 3 will always be published to PyPI. Any derivative packages can be hosted on <a href="http://fedorapeople.org" target="_blank">fedorapeople.org</a>. I'd like to defer to someone else to speak about the signing. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">______________________________<wbr>_________________<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<wbr>/listinfo/pulp-dev</a><br> <br></blockquote></div><br></div></div></div> <br>______________________________<wbr>_________________<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<wbr>/listinfo/pulp-dev</a><br> <br></blockquote></span></div><br></div></div> </blockquote></span></div><br></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>