[openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

Doug Hellmann doug.hellmann at dreamhost.com
Thu Jan 23 15:08:24 UTC 2014


On Wed, Jan 22, 2014 at 4:45 PM, Joe Gordon <joe.gordon0 at gmail.com> wrote:

>
>
>
> On Wed, Jan 22, 2014 at 5:19 AM, Julien Danjou <julien at danjou.info> wrote:
>
>> On Tue, Jan 21 2014, Joe Gordon wrote:
>>
>> > I would like to propose having a integration test job in Oslo incubator
>> > that syncs in the code, similar to how we do global requirements.
>>
>> I don't think that would be possible as a voting job, since the point of
>> oslo-incubator is to be able to break the API compatibility.
>>
>
> If oslo-incubator can break APIs whenever it wants how can a downstream
> project stay in sync with oslo-incubator?
>

"Usually the API maintainer or those making significant changes to an API
take responsibility for syncing that specific module into the projects
which use it" [1]

[1] https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator

That happens, AFAICT, when a known incompatibility is introduced. It does
not always happen when a compatible change is made. I'm really not sure of
the best way to improve that, other than to remind contributors to oslo of
the expectations.

Doug



>
>
>>
>> --
>> Julien Danjou
>> ;; Free Software hacker ; independent consultant
>> ;; http://julien.danjou.info
>>
>
>
> _______________________________________________
> 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/20140123/7b8cc7cc/attachment.html>


More information about the OpenStack-dev mailing list