Open Stack

On Thu, Jun 9, 2016 at 3:10 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>
>> On 10 Jun 2016, at 00:03, Sumit Naiksatam <sumitnaiksatam at gmail.com> wrote:
>>
>> On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>>
>>>> On 09 Jun 2016, at 11:16, Sumit Naiksatam <sumitnaiksatam at gmail.com> wrote:
>>>>
>>>> Hi Tony, The following repos should not be included in the EoL list since they will not be EoL'ed at this time:
>>>> openstack/group-based-policy
>>>> openstack/group-based-policy-automation
>>>> openstack/group-based-policy-ui
>>>> openstack/python-group-based-policy-client
>>>
>>> Would you mind clarifying why you absolutely need to maintain those old branches for those projects, and how do you plan to do it if no tempest jobs will be able to install other components for you?
>>>
>>
>> We are continuing to fix bugs for kilo users.
>
> How are you supposed to validate that those fixes don’t break interactions with other components?
>
We expect that any such fixes will be fairly contained, and well
covered by the UTs. In addition we will be doing our due diligence
with offline integration testing.

> Ihar
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev