On 07/16/2013 12:56 AM, Zhongyue Luo wrote:
> Gareth,
>
> https://wiki.openstack.org/wiki/Oslo#Principles
>
> I believe this link will answer most of your answers.
This is very topical, we've just been having a closely related discussion.
There is another class of common code and we're not sure
Gareth,
https://wiki.openstack.org/wiki/Oslo#Principles
I believe this link will answer most of your answers.
On Tue, Jul 16, 2013 at 11:16 AM, Gareth wrote:
> Michael, thanks for your perspective. It's easy to understand. But I just
> have some questions, not specific problems.
>
> Yaguang,
Michael, thanks for your perspective. It's easy to understand. But I just
have some questions, not specific problems.
Yaguang, I like the 'import' way too. But is there a global timeline of
making oslo mature? Is this decided by oslo team or release plan?
On Tue, Jul 16, 2013 at 11:00 AM, Yaguan
we put openstack common code in oslo
, and sync to other projects to keep the common code in each project is
aways up to date, when oslo is mature enough, then we will publish oslo as
a openstack common library. the common code in each project just need to
change from "from nova.openstack.common i
On Jul 15, 2013, at 7:22 PM, Gareth wrote:
> Hi, all
>
> There are some common codes in most of projects, such as opnstack/common, db,
> and some else (?). I know a good way is using 'import oslo' is ok, instead of
> copy those codes here and there. And now we already have project oslo and
>
Hi, all
There are some common codes in most of projects, such as opnstack/common,
db, and some else (?). I know a good way is using 'import oslo' is ok,
instead of copy those codes here and there. And now we already have project
oslo and trove, but how and when do we handle old codes, remove that