Open Stack

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 projects use newer versions of those libs.

Thanks,
Roman


On Wed, Oct 2, 2013 at 5:02 AM, ZhiQiang Fan <aji.zqfan at gmail.com> wrote:

> 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, then
> jenkins will propose a sync patch for projects listed in projects.txt
>
> this behavior will be dangerous, since it may pass gate test when merge
> but cause internal bug which is not well test coverd)
>
>
> On Wed, Oct 2, 2013 at 1:27 AM, Monty Taylor <mordred at inaugust.com> wrote:
>
>> Hey all!
>>
>> The job to automatically propose syncs from the openstack/requirements
>> repo went live today - as I'm sure you all noticed, since pretty much
>> everyone got a patch of at least some size.
>>
>> The job works the same way as the translations job - it will propose a
>> patch any time the global repo changes - but if there is already an
>> outstanding change that has not been merged, it will simply amend that
>> change. So there should only ever be one change per branch per project
>> in the topic openstack/requirements submitted by the jenkins user.
>>
>> If a change comes in and you say to yourself "ZOMG, that version would
>> break us" - then you should definitely go and propose an update to the
>> global list itself, which is in the global-requirements.txt file in the
>> openstack/requirements repo.
>>
>> The design goal, as discussed at the last two summits, is that we should
>> converge on alignment by the release at the very least. With this and
>> the changes that exist now in the gate to block non-aligned
>> requirements, once we get aligned, we shouldn't probably be too far out
>> from each other moving forward.
>>
>> Additionally, the list of projects to receive updates is managed in a
>> file, projects.txt, in the openstack/requirements repo. If you are
>> running a project and would like to receive syncing patches, feel free
>> to add yourself to the list.
>>
>> Enjoy!
>> Monty
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> blog: zqfan.github.com
> git: github.com/zqfan
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131002/22cf2617/attachment.html>