| 1 |
TODO list for reportbug 4.0 (squeeze): |
| 2 |
|
| 3 |
0. revisit README.{developers,source} for source code layout section |
| 4 |
|
| 5 |
0.1. fix the way reportbug/querybts obtain a UI: the ideal would be to |
| 6 |
use getUI from reportbug.ui, since the module already has all the |
| 7 |
UIs loaded (to know the ones available). |
| 8 |
bin/reportbug - line 833 |
| 9 |
bin/querybts - line 174 |
| 10 |
|
| 11 |
0.3. reportbug/ui/text_ui.py |
| 12 |
+ disabled utils.NEWBIELINE check to avoid circular import between text |
| 13 |
and utils ******** WE NEED TO FIND A SOLUTION TO THIS ********** |
| 14 |
|
| 15 |
0.4. check for utf-8/weird locales errors |
| 16 |
|
| 17 |
0.5. remove the tmp file only after the report is actually sent (or at least it |
| 18 |
should be configurable?) |
| 19 |
|
| 20 |
0.6. bin/reportbug: refactor the package name check/get/verify or so (now it's |
| 21 |
sparse all around the file |
| 22 |
|
| 23 |
0.7. what's the difference between 'X-Mailer' (as used by reportbug) and |
| 24 |
'User-Agent' (as used by bts)? what's preferred to identify the tool |
| 25 |
generating the email? |
| 26 |
|
| 27 |
3. BTS management interface for developers. You should be able to |
| 28 |
view the list of bug reports for a package, construct a list of |
| 29 |
actions, and produce one giant email to [email protected] to |
| 30 |
do that. Forwarding and merging, which both can be major PITAs, |
| 31 |
will be helpful. (See #157283) |
| 32 |
|
| 33 |
("devscripts" has the bts command. This is hence a very low priority.) |
| 34 |
|
| 35 |
4. i18n/l10n. |
| 36 |
|
| 37 |
(i18n/l10n with reportbug may not make much sense, since the |
| 38 |
reports have to be in English for most maintainers to understand |
| 39 |
them... unless we figure out some way to get bug reports translated |
| 40 |
for maintainers.) |
| 41 |
|
| 42 |
7. Allow followups from the command line using a specific bug number, |
| 43 |
rather than requiring people to go through the browser. Coupled |
| 44 |
with --query-only, this should allow me to drop querybts |
| 45 |
completely. (See #223335) |
| 46 |
|
| 47 |
8. Optionally display changelogs for new upstream versions. |
| 48 |
(See: #241552) Perhaps it should cooperate with apt-listchanges |
| 49 |
somehow to do this? |
| 50 |
|
| 51 |
9. Improve MUA code to allow arbitrary arguments to MUAs; see #271084. |
| 52 |
|
| 53 |
10. Multiple BTS support (again), which probably means "Bugzilla |
| 54 |
support" for Ubuntu, etc. |