Your message dated Thu, 24 Jan 2008 18:12:09 +0100
with message-id <[EMAIL PROTECTED]>
and subject line PTS: Please do not use experimental changelog
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: qa.debian.org
Hi,
On Thu, 2007-01-11 at 11:15 -0800, Thomas Bushnell BSG wrote:
> I was looking at the master changelog on packages.qa.debian.org. It's
> annoying that it doesn't track experimental and unstable separately.
I've been annoyed at this before and your message prompted me to
actually file a bug about it:
The PTS has links to the package's 'experimental' changelog. Please
change this to the unstable one. The PTS does this "right" for the
version number listed top-left, which is the unstable one.
From a qa perspective the unstable one is much more useful. Experimental
can be older or be completely different. Viewing the experimental
changelog could be optional, but the unstable one as the default one
seems sensible to me.
thanks,
Thijs
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
> The PTS has links to the package's 'experimental' changelog. Please
> change this to the unstable one. The PTS does this "right" for the
> version number listed top-left, which is the unstable one.
>
> From a qa perspective the unstable one is much more useful. Experimental
> can be older or be completely different. Viewing the experimental
> changelog could be optional, but the unstable one as the default one
> seems sensible to me.
I've just added a link from the "available versions" section to the
corresponding per-suite pages on packages.d.o. From there the
suite-specific changelog is available in 1 click.
In addition, I think that the experimental changelog link on the right
is the right thing. The reason is that it is *not* the experimental
changelog, but rather the "current" changelog (i.e. the latest
available). Being the PTS source oriented I believe that the latest
available is the right one to show if the request is not further
refined. To further refine it we have now the above mentioned
hyperlinks.
Hence, I'm closing the bug report with this mail.
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
[EMAIL PROTECTED],cs.unibo.it,debian.org} -<%>- http://upsilon.cc/zack/
(15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the
(15:57:15) Bac: no, la demo scema \/ right keys at the right time
signature.asc
Description: Digital signature
--- End Message ---
