-----BEGIN PGP SIGNED MESSAGE----- I think it is a good idea.
However, its implementation would be nearly equivalent to make longer the one-month period a closed bug is still kept in the bug database. If I remember well, the problem for this was disk space, so this may boil down to ask ourselves: Can we afford to spend one or two more extra Gigabytes on the bug system? (I assume Ian Jackson will be able to give more accurate numbers than "one or two G."). I can think of an intermediate solution, to save space: Whenever a bug is closed, the entire history of the bug is replaced by a "short history". Example: Bug #xxxx. Merged with #xxxx2 and #xxxx3. There was a typo in the extended description of the package. "yyyy" should be "zzzz". Closed: The typo was fixed in release foo-bar. "yyyy" was replaced by "zzzz". But this would be an extra work for the maintainers. I, for one, would not mind to write an abridged history of the bug when it is closed, but people who have still a lot of bugs to close will surely not like this procedure... -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQCVAgUBNMh9dCqK7IlOjMLFAQHJ0AP+LWqlcZEyjzrFpPt9KSIY+Daflf7OXUiB vVqDFYjMYWPRrrAaPYEm0R3EwlmzpI1aEiE8juHkebAI6UdJazXd8qxljl23t6+m BGlkcmbFKP/hgBfFCUcnt4rsvuAAKaDywrDVJDL9BABcm3tXzorzABRqqPfyuB8Q jA7nqA1AzNs= =5h0r -----END PGP SIGNATURE-----
