Sergii, Let's move this discussion to the thread "[Fuel] Changing APIs and API versioning". We need to have this mechanism regardless of our decision on API versioning.
2015-10-21 20:31 GMT+07:00 Sergii Golovatiuk <sgolovat...@mirantis.com>: > Vitaliy, > > Why do merge API changes without: > > 1. Fixing documentation? > 2. bumping API version? > > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Wed, Oct 21, 2015 at 3:08 PM, Vitaly Kramskikh <vkramsk...@mirantis.com > > wrote: > >> Hi, >> >> It's yet another time we broke fuelclient by merging a change >> <https://review.openstack.org/#/c/232021/> in fuel-web repo. Since we >> are considering moving Fuel UI to a separate repo, and we need to run UI >> functional tests against changes in nailgun anyway, I think we should start >> to change our CI so it could run tests from another repo against changes in >> another repo. >> >> Can it be done? >> >> -- >> Vitaly Kramskikh, >> Fuel UI Tech Lead, >> Mirantis, Inc. >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
