I have bulk moved all 268 issues slated for the mythical 3.4.x release
to an actual milestone so we can better plan things and start the usual
triage/prioritization. This will also prevent Max's jiralint job from
complaining should any of these issues be closed w/o updating the fix
If you would like subsequent milestones to be created (M2, M3) or
Beta/CR targets to be created, I can do so too - just ask!
For now though, it seems a bit premature as we don't have a schedule yet
for the 3.4 release stream. :)
If I moved an issue you had scheduled for fixVersion "3.3.x, 3.4.x" and
you want to move it back to the two targets, feel free. You might
instead want to use "3.3.1, 3.4.0.M1".
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio