1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
Short Term:
+ create a command that guess from the index.fwd list, every forwarded bug
it can handle, and that sets what needs to be
=> Sender has to be the usertag user here ==> archive
dirty solution is curently:
DEBEMAIL=$(user) ./btspull \
$(grep http ../db-h/index.fwd | \
sed -e 's/: .*/ / ; s/^/, /' | \
tr -d '\n' | sed -e 's/^, //')
+ have a website on http://bts-link.alioth.debian.org/
+ abort remote bts queues if too many failures
.oO( CPAN RT that is often down, and we wait 3 minutes per bug for a timeout )
Medium Term:
+ support more remote BTS
+ Implement duplicates following for non-Bugzilla BTS
+ Deal with merged bugs: do the commands once !
+ Create a btspull Maintainer-friendly version that will sets the
tags and do the forward, to avoid that work at the next cron run
(and makes the daily control mail smaller...)
+ Create some web pages that help to craft urls like the two on [4].
(those are crafted with the help of a preliminary work I did on
the kde bugs as a proof of concept a couple of weeks ago).
Long Term:
+ find a way to post new bugs, interactively or not. call that bzpush.py
config.cgi helps us a *lot* here.
|