[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Policy Weekly Issue #4/4: Announcing new packages before uploading them



Manoj Srivastava wrote:
> 	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.

I don't like overloading the changelog like this (no, I don't use release).
How about extending the changelog format so we have a field for closed bugs?
Something like:

foo (1.0-2) unstable; urgency=low closes=10002,11930,10109

  * Fix wibble() and splat() to not use bar().

 -- Joey Hess <joeyh@master.debian.org>  Sun, 26 Oct 1997 23:34:42 -0500

Then you don't have to worry about inaverdently closing bugs, and you don't
have any nastly looking thing in the changelog.

-- 
see shy jo


Reply to: