Re: Policy Weekly Issue #4/4: Announcing new packages before uploading them
Hi,
>>"Martin" == Martin Schulze <joey@finlandia.infodrom.north.de> writes:
>> i will like an automatic method to close bugs.
Martin> Let's take a look at the .changes files. Normally all
Martin> information is covered there. Normally closed bugs are
Martin> mentioned in the Changes: section. So Guys script should look
Martin> for #(\d+) and close $1 after proceeding (speaking in Perl).
Maybe a slightly stricter syntax for closing bugs, so I may
mention things like "This is similar to Bug#12345 on package xyz. We
are still lokking for a solution".
Maybe the check should eb for "This closes Bug#*** BUG#***"
(concatenatnig the line before the match, of course). This will
prevent spurious bug closures, and does not impose a major burden on
package maintainers.
manoj
--
It is the wise bird who builds his nest in a tree.
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: