Hi Martin, On Mon, Jun 8, 2009 at 07:17, martin f krafft<madd...@debian.org> wrote: > also sprach Sandro Tosi <mo...@debian.org> [2009.06.06.0836 +0200]: >> The solution I'd like to pursuit is: provide the whole set of BTS tags > > This means that whenever a new tag is added, you have to upload > a new reportbug, and that the information is redundantly stored also > in devscript's bts. I wonder if it weren't better not to do any > checks.
Let's put it this way: - tags are an official part on BTS and are defined by BTS admin (usertags are a different categorization, out of this problem); - tags don't change that ofter (except for "release" specific tags, that are private for rel team to set, and almost never done at submit time), so we can update the list when changes are applied and wait for a new upload to happen without too much worry and hurry; - since we should guarantee that reportbug works even offline, we cannot download the list all the times, so having a little replication of data (with a script to check for update) seems to reduce the impact of the problem. Hope this clarify the situation, but your suggestions are always welcome :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
