TODO - Perlbug TODO list
Speed improvements are probably the highest priority
I wonder if AUTOLOAD routines are a benefit while they're tidy and save lots of drossy code, they are the slowest methods and use up the most time (%), even when aliased into the symbol table and primed?
X-Perlbug: [ID ...]
Where:
[ID] = new ticket id has been assigned to this message
[ID*] = this is a reply to an existing non-open ticket
[ID+] = this is a reply to an existing open ticket
[ID-] = this is a reply to a ticket which has been deleted or is non-existent
Time related links on web overview, and check ratios
Full test suite
v3.5 Oracle support
Configurable template support dependent on context, object and user choice
Search functions for all discrete objects (currently it's all very bug oriented).
Better security model.
check modified status of db after create/delete of new object/relation
migrate userid from varchar->int
generate link from each section base to index/name/etc.
trim logs and ranges of unnecessary data
rationalise output ->
initial call with args...
intermittent results...
final results
$ret = relevant
-v = verbose -q = quiet
single wrapper to fix most things in the correct order a = things('mail')->check to and from's and cc's
remove 5.6.0. versions -> 5.6.0
trim redundant log and range info
done
script watches incoming mails reports if any bug, test, etc. don't land in p5p within one hour
done
message->reply, etc.
fixed in field is dodgy templates and search forms for each object
'new' form for each object
consistency:
bug_ids, bug_headers, bug_search...
status_ids, status_search
user_ids, user_search
Email suggestions to any of the following:
<a href="mailto:richard@perl.org">richard@perl.org</a>
<a href="mailto:perlbug@rfi.net">perlbug@rfi.net</a>
<a href="mailto:bugmongers@perl.org">bugmongers@perl.org</a>