<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 11, 2016 at 4:02 AM, Davanum Srinivas <span dir="ltr"><<a href="mailto:davanum@gmail.com" target="_blank">davanum@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Clay,<br>
<br>
Apologies for the top post. </blockquote><div><br></div><div>Oh goodness, none needed my friend!</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"><a href="https://github.com/openstack/requirements#global-requirements-for-openstack-projects" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>requirements#global-<wbr>requirements-for-openstack-<wbr>projects</a><br>
<br></blockquote><div><br></div><div>Eternal wells of gratitude for that read!  There was so many good gems in the review guidelines section!</div><div><br></div><div>Loved this bit:</div><div><span style="color:rgb(51,51,51);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol";font-size:16px"><br></span></div></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_quote">Everyone likes everyone else to use the latest version of their code. However, deployers really don't like to be constantly updating things. Unless it's actually impossible to use the minimum version specified in global-requirements.txt, it should not be changed.</div></div><div class="gmail_extra"><div class="gmail_quote"><br></div></div><div class="gmail_extra"><div class="gmail_quote">Leave that decision to deployers and distros.</div></div></blockquote><div class="gmail_extra"><div class="gmail_quote"><br></div><div class="gmail_quote"><a href="https://github.com/openstack/requirements#for-upgrading-requirements-versions">https://github.com/openstack/requirements#for-upgrading-requirements-versions</a><br><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">
There is a requirements team, you can reach them on the<br>
#openstack-requirements channel<br></blockquote><div><br></div><div>Cool I might stop by... Seems like there's some good knowledge to glean from the requirement team's experience and focus.</div><div><br></div><div>Even simple stuff like the links to different distro packaging search/status:</div><div><br></div><div><a href="https://github.com/openstack/requirements#finding-distro-status">https://github.com/openstack/requirements#finding-distro-status</a><br></div><div><br></div><div>... is very helpful!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://wiki.openstack.org/wiki/Requirements" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Requirements</a></blockquote><div><br></div><div>Hrmm... </div><div><span style="color:rgb(51,51,51);font-family:"arial unicode ms",arial,sans-serif;font-size:14px"><br></span></div></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_quote"><div>minor upstream version updates should be considered routine/cursory review</div><div> <br></div></div></div></blockquote><div class="gmail_extra"><div class="gmail_quote"><div><a href="https://wiki.openstack.org/wiki/Requirements#Review_Criteria">https://wiki.openstack.org/wiki/Requirements#Review_Criteria</a><br></div><div><br></div><div>Maybe my lens is off - seems like there's some conflicting attitudes on the wiki and the published guidelines on at least version bumps?</div><div><br></div><div>Also those guidelines focus mostly on the requirements team - not the program teams (which is more what I'm looking for right now).</div><div><br></div><div><div class="gmail_extra"><div class="gmail_quote"><div>There's the bit on the bot updates to requirements.txt:</div><div><br></div></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_quote">This is intended as a time saving device for projects, as they can fast approve requirements syncs and not have to manually worry about whether or not they are up to date with the global definition.</div><div class="gmail_quote"><br></div></div></blockquote><a href="https://github.com/openstack/requirements#automatic-sync-of-accepted-requirements">https://github.com/openstack/requirements#automatic-sync-of-accepted-requirements</a><br><div class="gmail_extra"><div class="gmail_quote"><br></div><div class="gmail_quote">But if it *is* just a connivence function what's the big deal that some projects (only swift?) are particularly sensitive to the minimum dependency version issue?</div><div class="gmail_quote"><br></div><div class="gmail_quote">There's the bit on the *process* of projects electing to participate in the very welcome and helpful requriements team review:</div><div class="gmail_quote"><br></div></div></div></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_quote"><div><div class="gmail_extra">This job ensures that a project can not change any dependencies to versions not compatible with global-requirements.txt</div></div></div></div></blockquote><div class="gmail_extra"><div class="gmail_quote"><div><div class="gmail_extra"><div class="gmail_quote"><br></div><div class="gmail_quote"><a href="https://github.com/openstack/requirements#enforcement-in-projects">https://github.com/openstack/requirements#enforcement-in-projects</a><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">... but  beyond "dependencies must meet the global requirements teams minimum bar and be added to global-requirements *first*" (which based on that teams review guidelines is *great* service to the community btw) - it's obviously meant to be just the starting point?  A proposed change to global requirements is supposed to reference the already in review change on the program code and the discussion about the appropriateness of outsourcing this impossible to live without functionality and coupling your project's fate to the dependency is obviously meant to happen by the program team?</div><div class="gmail_quote"><br></div><div class="gmail_quote">Is there any other information out there that's more focused on consistent guidelines for the *program* teams wrt to dependency hygiene - or is it cool everyone just sorta does their own thing within the bounds of reason (which are kept in check by the global requirements process)?<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">-Clay</div></div></div><div><br></div><div><br></div></div></div></div>