<div dir="ltr"><div><div>+1 to option 2.<br><br></div>If a pulp smash test is failing, it would be great if the full command to run exactly that test be posted on the bug. That would reduce the time it takes for a developer to resolve the issue.<br><br></div>Thanks for raising this.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 1, 2017 at 5:09 AM, 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">I like option 2, for all the reasons you said, and one more.<div><br></div><div>In trying to investigate the failure (if there are details about how it fails, I don't know where to see them), I noticed that the documentation for pulp_python is woefully inadequate. There are basic things missing, like information about how to construct a correct feed URL. The only docs with any substantial information are the "Getting Started" docs, which only show examples.</div><div><br></div><div>I think there's at least a decent chance that the test is failing because QE had to make guesses about how to construct a feed URL, and happened to guess wrong. Looking at the docs in their current state, I would not want to be responsible for writing tests for this plugin. QE: please feel empowered to complain about missing docs. I feel bad that you were working from so little information.</div><div><br></div><div>It would be much better to release pulp_python 2.0 with at least basic documentation for its features. Let's take some time and get that right, while not blocking Pulp 2.12.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Michael</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 1, 2017 at 3:24 AM, Jen Albertson <span dir="ltr"><<a href="mailto:jalberts@redhat.com" target="_blank">jalberts@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>My only opinion is that we do not block the release of 2.12 on pulp_pytho 2.0 (so concurring with you option 2). </div><div><br></div><div>I'm interested to hear what other thoughts there are as to when and how we introduce it. </div><div><br><div class="gmail_quote"><div><div class="m_-3785442043093335841h5"><div>On Tue, Jan 31, 2017 at 5:57 PM Sean Myers <<a href="mailto:sean.myers@redhat.com" target="_blank">sean.myers@redhat.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-3785442043093335841h5">2.12.0 has generally passed upgrade testing, but this guy over in pulp_python<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>land got kicked back to us:<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><a href="https://pulp.plan.io/issues/140" rel="noreferrer" class="m_-3785442043093335841m_-4673495781402555288gmail_msg" target="_blank">https://pulp.plan.io/issues/14<wbr>0</a><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>That's one of the new pulp_python 2.0 features. We have a few options for<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>how to proceed, so I thought it would be worthwhile to put those options<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>to the list and decide what to do.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>1. Release pulp 2.12.0 with pulp_python 2.0, with a known issue stating that<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> this feature is broken, and will be fixed "soon". Pulp 2.12.0 is released<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> tomorrow.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>2. Release pulp 2.12.0 with pulp_python 1.1.3, the current stable version,<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> deferring the pulp_python 2.0 release until a later date. Pulp 2.12.0<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> is released tomorrow.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>3. Release pulp 2.12.0 with pulp_python 2.0, but remove the new feature from<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> the list of features added in pulp_python 2.0. Pulp 2.12.0 is released<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> tomorrow, pulp_python 2.1 is released at a later date with this new feature<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> included.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>4. Block the release of pulp 2.12.0 pending the fix and verification of<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> this story, release pulp 2.12.0 with pulp_python 2.0. Pulp 2.12.0 release<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> date is undefined.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>5. Something else I haven't suggested here.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>Among this options, I prefer the second, since it means we do release very<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>close to our target release date, and don't release known-broken stuff.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>Given that pulp is able to sync from the "real" pypi, if pulp isn't able to sync<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>a pypi-like repository published by pulp itself, that suggests to me that more<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>features may be at risk in pulp_python 2.0 than the ability to sync from pulp.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>I would prefer to mitigate that risk by *not* releasing pulp_python 2.0 without<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>more verification.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>Both options 1 and 2 give us a little bit of flexibility. Some examples:<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>- We could do a separate release cycle for only the updates to pulp_python,<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> following a similar process to what we do for platform Y-releases. This is<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> nice, but may result in a very surprising major-version upgrade of a package<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> between pulp platform releases.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>- We could release pulp_python 2.0 with pulp 2.13.0. This is less surprising,<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> but also delays the new features introduced in pulp_python 2.0 for still<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> another platform Y-release.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>- We could do a hybrid of the two, such as releasing a functioning pulp_python<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> 2.0 in its own repository with special instructions for installation, and then<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br> bundle pulp_python 2.0 with 2.13.0 as we had intended to do with 2.12.0.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>So, my questions (and my current answers to them) are these:<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>- Do we want to block the release of pulp 2.12.0 until pulp_python is ready to<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>release? (I expect that we do not.)<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>- Do we want to release pulp_python 2.0 tomorrow, with 2.12.0, knowing that it<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>is *not* feature-complete? (I'm less confident here, but suspect that we don't<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>want to release pulp_python 2.0 in a non-working state.)<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>- Do we want to release pulp_python 2.0 at some point before the release of pulp<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>2.13.0? (I'm mostly indifferent here. I think it would trivial to put together a<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>release of just pulp_python 2.0 that can be made generally available prior to the<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>release of pulp, but I don't know how useful that would actually be. We also may<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>not need to decide this right now, depending on other answers.)<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>Given no objections, my current plan is to follow option #2, and release pulp<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>2.12.0 tomorrow afternoon with pulp_python 1.1.3, and we can decide what to do<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>about pulp_python 2.0 afterward.<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>Thanks for reading my novel. :)<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br></div></div>______________________________<wbr>_________________<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br>Pulp-dev mailing list<br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><a href="mailto:Pulp-dev@redhat.com" class="m_-3785442043093335841m_-4673495781402555288gmail_msg" target="_blank">Pulp-dev@redhat.com</a><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br><a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" class="m_-3785442043093335841m_-4673495781402555288gmail_msg" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br class="m_-3785442043093335841m_-4673495781402555288gmail_msg"><br></blockquote></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></div><br></div> </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>