Open Stack

Hi,

+1 to Evgeniy... Since 'critical' and 'high' were cleared up from SCF to
Release we should assume that new Cricital and High bugs are introduced by
'new' features. In this case feature team should fix it.

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Fri, Oct 2, 2015 at 10:01 AM, Evgeniy L <eli at mirantis.com> wrote:

> Hi Dmitry,
>
> Thanks for the information.
>
> >> My personal opinion is that we can ignore our medium-priority
> technical debt bugs for now. We should fix them but there is nothing that
> cannot be postponed here. We will continue fixing them in background. The
> only exception here should be bugs related to alignment with global
> requirements, tox and oslo-related changes. We definitely should fix this
> stuff.
>
> I think we shouldn't ignore medium priority tech debt bugs now, the
> beginning of the release
> cycle is the best time to fix them.
>
> Thanks,
>
> On Thu, Oct 1, 2015 at 9:17 PM, Dmitry Pyzhov <dpyzhov at mirantis.com>
> wrote:
>
>> Guys,
>>
>> I was not able to participate in our weekly IRC meeting. So I'd like to
>> share our bug status for 8.0 release with offline e-mail.
>>
>> We have 494 Fuel bugs on Launchpad. This number can be splitted into
>> several piles.
>>
>> 1) Critical and High priority bugs. We have 48 of them now. 2 in UI, 31
>> in python, 15 in library. Here is our focus and we are working on reducing
>> the numbers.
>> 2) Medium/Low/Wishlist priority bugs. We have 241 bug. 72 in UI, 119 in
>> python, 50 in library.
>> 3) Features reported as bugs and bugs that can be fixed only by
>> implementing new blueprints. We have 133 of them. 3 in UI, 106 in python
>> and 24 in library. These bugs are marked with 'feature', 'covered-by-bp'
>> and 'need-bp' tags. Numbers look scary but only 40 of them have high and
>> critical priority.
>> 4) Technical debt. Things that we should do better from developer's point
>> of view. 72 bugs in total. 60 in python, 12 in library. They are marked
>> with 'tech-debt' tag.
>>
>> My personal opinion is that we can ignore our medium-priority technical
>> debt bugs for now. We should fix them but there is nothing that cannot be
>> postponed here. We will continue fixing them in background. The only
>> exception here should be bugs related to alignment with global
>> requirements, tox and oslo-related changes. We definitely should fix this
>> stuff.
>>
>> You can see that we have big demand for python developers. Here is my
>> early estimation. With current pace we can fix all existing library bugs in
>> 8.0. Also we can fix all existing high priority bugs in python. It includes
>> technical debt and maybe feature-bugs. It looks like we are able to fix
>> about half of medium priority python bugs. I don't have any estimations for
>> medium priority feature-bugs in python. And I'd prefer to be pessimistic
>> here. Also we will fix very small number of medium priority technical debt
>> bugs.
>>
>> There is a good chance that number of incoming bugs will became smaller
>> over time and we will fix most of existing medium priority python bugs.
>>
>> __________________________________________________________________________
>> 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
>>
>>
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151002/9ce71153/attachment.html>