Yep, Roman,
mos LP project was just created. So let's inform everyone to use it for
components bugs, and not forgetting about tags.
On Thu, Jun 19, 2014 at 9:37 AM, Roman Podoliaka rpodoly...@mirantis.com
wrote:
Hi guys,
Dmitry, I have nothing against using 'also affects', but
Hi Fuelers,
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
Roman,
What do you think about adding OS projects into the bug as also affects?
That allows to track upstream and downstream state of the bug separately
while maintaing visibility of both on the same page. The only downside is
spamming the bug with comments related to different projects, but I
+1 to this approach.
Actually we've just created separate LP project for MOS:
https://launchpad.net/mos,
and all bugs related to openstack / linux code (not Fuel), should be
tracked there.
I still think that we should also adding other OpenStack projects by
clicking on also affects where possible.
Actually I agree on tagging bugs as Roman suggests.
If no one against, we can create official tags for every project (nova,
neutron, etc.) - as long as it simplifies life and easy to use, I'm all for
it.
On Thu, Jun 19, 2014 at 6:26 AM, Mike Scherbakov mscherba...@mirantis.com
wrote:
+1 to
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
Fuelers,
please pay attention to stalled in progress bugs too - those which are In
progress for more than a week. See [1].
[1]
Current count:
New - 56
Incomplete - 48
Confirmed/Triaged/In progress for 5.1 - 331
Fuelers,
as we discussed during last IRC meeting
http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-06-12-16.01.html,
I'm scheduling bug squashing day on Tuesday, June 17th.
I'd like to propose the following order of bugs processing:
1. Confirm / triage bugs in New status
