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.
Jay On Jan 8, 2015 12:03 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > > On Jan 8, 2015, at 11:29 AM, Ihar Hrachyshka <ihrac...@redhat.com> > wrote: > > > > On 01/05/2015 04:51 PM, Doug Hellmann wrote: > >> 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. > > > > 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? > > 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. > > Doug > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev