Re: Accepted valknut 0.3.7-1 (i386 source)

[Martin Zobel-Helas <zobel@ftbfs.de>]

Hi Pasi,

On Saturday, 19 Mar 2005, you wrote:
> Kirjoitit viestissäsi (lähetysaika lauantai, 19. maaliskuuta 2005 02:53):
> > On Friday, 18 Mar 2005, you wrote:
> > > Changes:
> > >  valknut (0.3.7-1) unstable; urgency=high
> > >  .
> > >    * New upstream release (Closes: #289643, #269952, #265284, #270096,
> > > #286234)
> >
> > is there any reason for not giving some more explanation, when closing
> > bugs with urgency=high and only listing "New upstream release" as
> > only changelog entry.
> >
> > I would like to have some more explanation for this in the changelog.
> >
> hello Martin,
> There really isn't any more to say. There is nothing else changed in package 
> than new source so I don't really know what else I could say. priority High 
> is since dcgui-qt is totally unusable with new libxml AND if one tries to 
> start dcgui-qt with new libxml it destroys ones dcqui-qt config file. But 
> again nothing changed in package. just recompile against new libxml would 
> remove those unusability issues. oh, one thing I should had said was that I 
> updated man page to match new name, but I forgot it because I made it when I 
> was working with 0.3.3.

please don't take my last eMail as offence. Let me explain a little bit:
i am reading debian-devel-changes, so i saw your upload. And i was a 
little bit irritated, when i saw "urgency=high", but the only 
changelog-entry was "New upstream version" with some "Closes" in it. As
reader, it was not clear for me why a new upstream version justifies 
"urgency=high", so i had to look in the BTS. I just took a quick look 
and didn't find any serious or grave bugs fixed, which irritated me even
more.

Lets imagine we are already in freeze and your package would have been 
uploaded to testing-proposed-updates(t-p-u). As all packages on t-p-u 
will be reviewed before letting in, it is easier for the reviewer, if 
the changelog says something like that:

valknut (0.3.7-1) unstable; urgency=high

  * New Upstream version
    - fixes random data loss (Closes: 12345), therefore urgency high
    - fixes foo
    - fixes bar
    ....


The reviewer sees within the first two lines of the changelog the 
essential data: a) it is new upstream b) it fixes something very 
important, which justifies the urgency.


Hope that helps and i hope i annoied you not too much.

Greetings
Martin