agree, that's a decent way
2017-02-09 21:24 GMT+08:00 Doug Hellmann :
> Excerpts from ChangBo Guo's message of 2017-02-09 15:21:55 +0800:
> > I just added it in https://etherpad.openstack.org/p/community-goals
> > yesterday. submit a community goal for this ?
>
> Someone
Excerpts from ChangBo Guo's message of 2017-02-09 15:21:55 +0800:
> I just added it in https://etherpad.openstack.org/p/community-goals
> yesterday. submit a community goal for this ?
Someone needs to start documenting the sort of work needed (how many
projects use mox3, and how much) and putting
I just added it in https://etherpad.openstack.org/p/community-goals
yesterday. submit a community goal for this ?
2017-02-09 3:20 GMT+08:00 Doug Hellmann :
> Excerpts from Joshua Harlow's message of 2017-02-08 10:01:27 -0800:
> > Doug Hellmann wrote:
> > > Excerpts from
Excerpts from Joshua Harlow's message of 2017-02-08 10:01:27 -0800:
> Doug Hellmann wrote:
> > Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800:
> >> Thanks Doug and amoralej, we should avoid this :(.
> >>
> >> One more thought about mox3: Is it used outside of OpenStack? If yes,
Doug Hellmann wrote:
Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800:
Thanks Doug and amoralej, we should avoid this :(.
One more thought about mox3: Is it used outside of OpenStack? If yes,
Maybe we can retire mox3 if all projects move mox to mock.
I thought our policy was
Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800:
> Thanks Doug and amoralej, we should avoid this :(.
>
> One more thought about mox3: Is it used outside of OpenStack? If yes,
> Maybe we can retire mox3 if all projects move mox to mock.
I thought our policy was that mox3 was
Thanks Doug and amoralej, we should avoid this :(.
One more thought about mox3: Is it used outside of OpenStack? If yes,
Maybe we can retire mox3 if all projects move mox to mock.
2017-02-07 23:00 GMT+08:00 Doug Hellmann :
> The stable/ocata branch for mox3 was created
The stable/ocata branch for mox3 was created from 0.19.0 and then 0.20.0
was released from master. Because that repository sees a very low rate
of changes, and because the current stable/ocata branch only contained
the patch to update the .gitreview file, we decided to recreate the
branch to