Hello ZhiQiang,
I'm not sure what HEADs you mean: oslo-incubator doesn't contain git
submodules, but rather regular Python packages.
On the other hand, oslo.version/oslo.messaging/oslo.* are separate
libraries, having their own releases, so syncing of global requirements
will effectively make
Hi, Roman,
auto sync requirements is a good job.
It is so good that I'm wondering if the oslo-incubator can do such job too,
because i noticed that there are some patches just update oslo-incubator
modules, (no related bug, just normal update, sorry i cannot remember
specific example), sometimes
Requirements is a little different, because we actually know in advance
that the code will work with the latest requirements before we propose
the change to the projects, as the requirements changes are gated on
tempest/devstack.
proposed changes to oslo don't attempt to run them against all
Hi, Sean Dague,
Thank you for the clarification.
On Wed, Oct 2, 2013 at 7:44 PM, Sean Dague s...@dague.net wrote:
Requirements is a little different, because we actually know in advance
that the code will work with the latest requirements before we propose the
change to the projects, as the
On 2013-10-02 07:44:11 -0400 (-0400), Sean Dague wrote:
Requirements is a little different, because we actually know in
advance that the code will work with the latest requirements before
we propose the change to the projects, as the requirements changes
are gated on tempest/devstack.
[...]
great job! thanks
(how about auto sync from oslo too?
- projects.txt: projects want to be automatically synced from oslo
- heads.txt: HEAD for each module in oslo
whenever module maintainer think current module is strong enough to
publish, then he/she can edit the heads.txt of that module line,
