Excerpts from Ben Nemec's message of 2013-08-16 11:10:09 -0700: > On 2013-08-16 11:58, Jay Pipes wrote: > > On 08/16/2013 09:52 AM, Boris Pavlovic wrote: > >> Hi all, > >> > >> We (OpenStack contributors) done a really huge and great work around > >> DB > >> code in Grizzly and Havana to unify it, put all common parts into > >> oslo-incubator, fix bugs, improve handling of sqla exceptions, provide > >> unique keys, and to use this code in different projects instead of > >> custom implementations. (well done!) > >> > >> oslo-incubator db code is already used by: Nova, Neutron, Cinder, > >> Ironic, Ceilometer. > >> > >> In this moment we finished work around Glance: > >> https://review.openstack.org/#/c/36207/ > >> > >> And working around Heat and Keystone. > >> > >> So almost all projects use this code (or planing to use it) > >> > >> Probably it is the right time to start work around moving oslo.db code > >> to separated lib. > >> > >> We (Roman, Viktor and me) will be glad to help to make oslo.db lib: > >> > >> E.g. Here are two drafts: > >> 1) oslo.db lib code: https://github.com/malor/oslo.db > >> 2) And here is this lib in action: > >> https://review.openstack.org/#/c/42159/ > >> > >> > >> Thoughts? > > > > ++ > > > > Are you going to create a separate Launchpad project for the library > > and track bugs against it separately? Or are you going to use the oslo > > project in Launchpad for that? > > At the moment all of the oslo.* projects are just grouped under the > overall Oslo project in LP. Unless there's a reason to do otherwise I > would expect that to be true of oslo.db too.
Has that decision been re-evaluated recently? I feel like bug trackers are more useful when they are more focused. But perhaps there are other reasons behind using a shared bug tracker. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
