Things to do, ordered roughly in the order of importance.
* Prepare slides for 27 Jan presentation
This can be combined with performing further work on
deployment doc and design doc:
* Deployment doc: prepare unsuspecting vict^W^W user/admin
who installs and uses abrt for the first time what to expect.
It needs to answer user-centric information about "How Do I Do X?
How Do I Do Y?". Example doc for yum:
Douglas Silas <dhensley(a)redhat.com> may help with review
* Design doc needs updating/consolidating:
doc/DESIGN and https://fedorahosted.org/abrt/wiki/AbrtArchitecture
(some of the above is already done)
* Make it possible to disable backtrace production for binary crashes:
- add an option to ccpp analyzer to not download debuginfos
and not run gdb
- move gdb dependency from ccpp plugin to abrt-desktop package
* Jirka: teach other members of the team how to do releases,
to reduce his own workload
* Further improve dup detection - have two hashes computed:
one for "good" backtraces, one for "bad", and check for match
of either one against reports already stored in BZ.
If either has a match, then it's a dup.
This makes most "bad" backtraces be grouped into one dup per
* Fix more bugs before RHEL branch is cut (15 Jan).
We have plenty of work for us in the BZ...
* Retrace server:
- see how it is done by other projects (Ubuntu/Ffox/etc):
- start implementing one
- when, and *if*, it looks like it is a step forward,
not an additional burden, then consider officially
adding it to abrt.