I tend to use the JIRA reporting scheme to find issues by Component, so
for me it is helpful to have a component assigned to every issue. I
took a stab a categorizing the 50 odd issues that had no component,
sorry for the bandwith for those who get all those messages.
As Dan already corrected, I just took a quick stab - if you think I got
it wrong feel free to change. I got the non-component list down to 2.
I can't figure out how to get DERBY-590 off, I assigned it a component -
but my guess is it's linking is confusing something. I just couldn't
come up with a place for the eclipse issue DERBY-631.
It felt most unsatisfying assigning a lot of issues to SQL, which really
are internal "sql execution" issues. And if we had the categories a lot
I could have assigned to optimizer, parser, execution.
