comparison database/schema/TODO @ 24:ae420ef170e4

Update.
author David A. Holland
date Sun, 26 May 2013 18:33:11 -0400
parents 68cc276ac118
children 233dcc4d80e1
comparison
equal deleted inserted replaced
23:ca4679ac4e02 24:ae420ef170e4
1 -- Does not handle: 1 -- Does not handle:
2 --
3 -- * The Description, How-To-Repeat, and Fix fields from gnats are
4 -- supposed to just be the initial entries in the message log, but
5 -- they're currently also in the bugs table. Also "unformatted".
6 --
7 -- * There is no administrative queue yet.
8 -- - comments on locked PRs
9 -- - comments on nonexistent PRs
10 -- - bounced mail from feedback requests
11 -- - other bounced mail
12 -- - unreocgnized/junk/malformed mail?
13 -- - action requests in commit messages like Christos wants
14 --
15 -- * "Category" is just a classification scheme, but we need to know
16 -- (based on the category) what default subscriptions to create.
17 -- There's currently no way to do this. Since the script for
18 -- accepting incoming PRs needs to know about the gnats schema
19 -- anyway, perhaps there should just be a table in the database to
20 -- tell it what to do.
21 --
22 -- * There also needs to be a hook to deduce the package name for
23 -- pkgsrc PRs by scanning the synopsis. This is going to be netbsd-
24 -- specific; making it table-driven isn't feasible and probably it's
25 -- not worth (at least at first) setting up a whole scheme for
26 -- site-specific extensions. So probably it'll be hard-coded in at
27 -- least to begin with.
28 --
29 -- * There should be an incoming queue for stuff submitted via the web
30 -- interface, because a lot of it will be spam.
31 --
32 -- * There should be a whitelist/blacklist for that queue, by IP
33 -- address or netblock.
34 --
35 -- * Should support automatic feedback timeout.
36 --
37 -- (the stuff below this point probably isn't getting done before the
38 -- initial deployment)
2 -- 39 --
3 -- * Should be able to merge duplicates. 40 -- * Should be able to merge duplicates.
4 -- * Should allow recording dependencies between bugs. 41 -- * Should allow recording dependencies between bugs.
5 -- * Category should list the default 'responsible' value. 42 -- * Should store pullup numbers
6 -- * Need to know what relevance entries to create based on the category. 43 --
7 -- * There should be an incoming queue for stuff submitted via the web
8 -- interface, because a lot of it will be spam.
9 -- * There should be a whitelist/blacklist for that queue, by IP address
10 -- or netblock.
11 -- * Should support automatic feedback timeout.
12 -- * should store pullup numbers