[openstack-dev] [all][trove] Trove bug scrub

Mariam John mariamj at us.ibm.com
Sat Apr 9 14:06:43 UTC 2016


Thanks Amrith for going through the list and triaging the bugs. I think
it's a great thing that we now have bugs assigned as 'low-hanging-fruit'.
It should make it easier for newcomers to pick bugs and get started.

Regards,
Mariam.




From:	Amrith Kumar <amrith at tesora.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>
Date:	04/05/2016 03:59 PM
Subject:	Re: [openstack-dev] [all][trove] Trove bug scrub




From: Victoria Martínez de la Cruz [mailto:victoria at vmartinezdelacruz.com]
Sent: Tuesday, April 05, 2016 4:35 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [all][trove] Trove bug scrub

Thanks Amrith.

I'll follow your lead and do some triaging as well.

We should organize bug triage days to make this process easier next time.

[amrith] I’ve been meaning to do this for some time and this morning I
finally got around to it. But in the future, it would be good to stay ahead
of this so we don’t have so much of backlog.

How about bug fixing days or bug squashing days? I’d love to do that as
well and further trim the backlog.

2016-04-05 14:44 GMT-03:00 Flavio Percoco <flavio at redhat.com>:
 On 05/04/16 15:15 +0000, Amrith Kumar wrote:
  If you are subscribed to bug notifications from Trove, you’d have
  received a
  lot of email from me over the past couple of days as I’ve gone through
  the LP
  bug list for the project and attempted to do some spring cleaning.



  Here’s (roughly) what I’ve tried to do:



  -    many bugs that have been inactive, and/or assigned to people who
  have not
  been active in Trove for a while have been updated and are now no longer
  assigned to anyone

  -    many bugs that related to reviews that have been abandoned at some
  time
  and were marked as “in-progress” at the time are now updated; some are
  marked
  ‘confirmed’, others which appear to be no longer the case are set to
  ‘incomplete’

  -    some bugs that were recently fixed, or are in the process of getting
  merged have been nominated for backports to mitaka and in some cases
  liberty

 Awesome! I'll go through the backport reviews.
  Over the next several days, I will continue this process and start
  assigning
  meaningful milestones for the bugs that don’t have them.



  There are now a number of bugs marked as ‘low-hanging-fruit’, and several
  others that are unassigned so please feel free to pitch in and help with
  making
  this list shorter.

 ++

 Flavio

 --
 @flaper87
 Flavio Percoco

 __________________________________________________________________________
 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/20160409/fc686d1d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160409/fc686d1d/attachment.gif>


More information about the OpenStack-dev mailing list