<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    OK, I was going to implement something for neutron, but if you're
    going to handle it quickly till the end of the week, I'll wait to
    steal. ;)<br>
    <br>
    <div class="moz-cite-prefix">On 01/08/2015 07:14 PM, Jay Bryant
      wrote:<br>
    </div>
    <blockquote
cite="mid:CA+0S5sQFaCVY_V8WTNt4=CQeiqhPSa7VwK3hN4X8Eq1+PC_i0g@mail.gmail.com"
      type="cite">
      <p dir="ltr">We talked about this in Cinder.  I am planning to
        create some hacking checks for us just to be safe.   Shouldn't
        take a ton of effort. </p>
      <p dir="ltr">Jay</p>
      <div class="gmail_quote">On Jan 8, 2015 12:03 PM, "Doug Hellmann"
        <<a moz-do-not-send="true"
          href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
          > On Jan 8, 2015, at 11:29 AM, Ihar Hrachyshka <<a
            moz-do-not-send="true" href="mailto:ihrachys@redhat.com">ihrachys@redhat.com</a>>
          wrote:<br>
          ><br>
          > On 01/05/2015 04:51 PM, Doug Hellmann wrote:<br>
          >> As each library is released, we will send release
          notes to this list, as usual. At that point the Oslo liaisons
          should start planning patches to change imports in their
          projects from "oslo.foo" to “oslo_foo". The old imports should
          still work for now, but new features will not be added to the
          old namespace, so over time it will be necessary to make the
          changes anyway. We are likely to remove the old namespace
          package completely during the next release cycle, but that
          hasn't been decided.<br>
          ><br>
          > Making the switch probably requires us to add some
          hacking rule that would forbid old namespace based imports,
          right? Do we by chance have such a rule implemented anywhere?<br>
          <br>
          I’m not sure that’s something we need to enforce. Liaisons
          should be updating projects now as we release libraries, and
          then we’ll consider whether we can drop the namespace packages
          when we plan the next cycle.<br>
          <br>
          Doug<br>
          <br>
          <br>
          _______________________________________________<br>
          OpenStack-dev mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
          <a moz-do-not-send="true"
            href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
            target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>