we should all review the open issues that we have, and decide on them,
which are:

- by now fixed or non-relevant issues (close them)
- duplicate issues (place a note that it's a duplicate, close it)
- simple bugs (mark for milestone 1.0.x)
- bugs to be fixed by 1.1 (mark for milestone 1.1)
- features:
- to be included in 1.1 (mark for milestone 1.1)
- to be implemented later (leave in milestone future)


as we had issues scattered in various milestones, I've made some
re-organization. I crated a catch-all milestone called 'future', and
I've put all peding issues there. (I didn't manage to process all issues
that were not assigned to any milestone yet, so you'll see some more).

in total, we have 165 issues open. but don't worry, there are a lot of
duplicated, and a lot that seem to have been solved by then (just not
close for some reason)

please look at the issues which:

- have been already assigned to you
- are related to 'your' component
- you have submitted a long while ago, and is still open
(there's a good chance these are stale bugs)


after classifying the issues as above, please spend some time evaluating
how difficult they are, how much effort it would be to solve them. for
each of these estimates, please put a note into the issue itself.

please also mark if there is serious uncertainity / risk involved with
an issue. this might arise from a lack of detailed knowledge about the
issue, an untried library involved, etc. if an issue is risky, just put
a note like "high risk" along the resource estimate. naturally, such
issues can not be estimated too well.


I also updated the list of components one can associate an issue with.
the new list is the following:

Name Owner
----------------------------------
End-user Documentation micz
HTML UI sebastian
LS-Knoppix Install CD douglas
scheduler server maroy
gLiveSupport fgerlits
storage server tomash
localizer sebastian
packaging maroy
development environment maroy



please refrain from using old categories (like 'server feature', instead
of that use 'storage server' or 'scheduler server' with severity 'feature')