[openstack-dev] [Fuel] Bug squashing day on June, 17
rpodolyaka at mirantis.com
Wed Jun 18 09:04:25 UTC 2014
Not directly related to bug squashing day, but something to keep in mind.
AFAIU, both MOS and Fuel bugs are currently tracked under
https://bugs.launchpad.net/fuel/ Launchpad project page. Most bugs
filed there are probably deployment-specific, but still I bet there is
a lot of bugs in OS projects you run into. If you could tag those
using OS projects names (e.g. you already have the 'neutron' tag, but
not 'nova' one) when triaging new bugs, that would greatly help us to
find and fix them in both MOS and upstream projects.
On Wed, Jun 18, 2014 at 8:04 AM, Mike Scherbakov
<mscherbakov at mirantis.com> wrote:
> please pay attention to stalled in progress bugs too - those which are In
> progress for more than a week. See .
> On Wed, Jun 18, 2014 at 8:43 AM, Mike Scherbakov <mscherbakov at mirantis.com>
>> Thanks for participation, folks.
>> Current count:
>> New - 12
>> Incomplete - 30
>> Confirmed / Triaged / in progress for 5.1 - 368
>> I've not logged how many bugs we had, but calculated that 26 bugs were
>> filed over last 24 hours.
>> Overall, seems to be we did a good job in triaging, but results for fixing
>> bugs are not that impressive. I'm inclined to think about another run, let's
>> say, next Tuesday.
>> On Tue, Jun 17, 2014 at 7:12 AM, Mike Scherbakov
>> <mscherbakov at mirantis.com> wrote:
>>> Current count:
>>> New - 56
>>> Incomplete - 48
>>> Confirmed/Triaged/In progress for 5.1 - 331
>>> Let's squash as many as we can!
>>> On Mon, Jun 16, 2014 at 6:16 AM, Mike Scherbakov
>>> <mscherbakov at mirantis.com> wrote:
>>>> as we discussed during last IRC meeting, I'm scheduling bug squashing
>>>> day on Tuesday, June 17th.
>>>> I'd like to propose the following order of bugs processing:
>>>> Confirm / triage bugs in New status, assigning them to yourself to avoid
>>>> the situation when a few people work on same bug
>>>> Review bugs in Incomplete status, move them to Confirmed / Triaged or
>>>> close as Invalid.
>>>> Follow https://wiki.openstack.org/wiki/BugTriage for the rest (this is
>>>> MUST read for those who have not done it yet)
>>>> When we are more or less done with triaging, we can start proposing
>>>> fixes for bugs. I suggest to extensively use #fuel-dev IRC for
>>>> synchronization, and while someone fixes some bugs - the other one can
>>>> participate in review of fixes. Don't hesitate to ask for code reviews.
>>>> Mike Scherbakov
>>> Mike Scherbakov
>> Mike Scherbakov
> Mike Scherbakov
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev