Let's not flip bits back and forth, please discuss first instead of reversing something I just did.
I agree that it's a hard-to-trigger bug, but if we have an uncomplicated fix for it, it's fine w/ me to go into a point release. If it required a major re-architecting to fix then I'd agree that we could just let it be in 2.1.x and fix it in 2.2.x.
In that case, I'd put it in both series, mark it WontFix in the 2.1 series so we document the decision, and add it to 2.2.0 milestone in the 2.2 series. Since you removed all series and milestones, this bug is floating in the void and we'll probably forget about it. :(
A crash bug is always critical importance. See: /www.mixxx. org/wiki/ doku.php/ launchpad_ bugs#bug_ importance_ guidelines
https:/
Let's not flip bits back and forth, please discuss first instead of reversing something I just did.
I agree that it's a hard-to-trigger bug, but if we have an uncomplicated fix for it, it's fine w/ me to go into a point release. If it required a major re-architecting to fix then I'd agree that we could just let it be in 2.1.x and fix it in 2.2.x.
In that case, I'd put it in both series, mark it WontFix in the 2.1 series so we document the decision, and add it to 2.2.0 milestone in the 2.2 series. Since you removed all series and milestones, this bug is floating in the void and we'll probably forget about it. :(