On Sat, Mar 07, 2009 at 02:01:31PM -0000, Peter Maydell wrote:
> > Is this issue still reproducible in Jaunty with Xfce 4.6?
>
> Presumably you have a Jaunty system; wouldn't it be better to take the
No, I don't have a jaunty system (Debian testing).
> 60 seconds to follow the instructions for reproduction in the original
> bug report (as modified to allow for the fact that the specific package
> has been removed so presumably it's some other config utility) to find
> out whether this bug is still a problem? Then you could say something
I already checked before asking, and I couldn't find the sliders you
were speaking of. Since I don't often use these dialogs, I chose not to
close the bug report directly (I could have missed them). But thanks
anyway, for trying to explain me what I should do while I'm already doing
it.
> like "The new display preferences utility in Jaunty is <foobar>; I
> checked and it doesn't have this bug." which is much more useful and
> informative and less likely to irritate bug submitters by sounding like
> a pointless health-check message; and then you would be able to actually
> close the bug...
These posts mostly describe interactions between bug triagers and
developers. I uploaded almost all Xfce 4.6 packages into jaunty. So,
should my developer self bash my bug triager self?
But here is the standard response I should have pasted here when closing
the bug instead of asking for input:
"
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu - the Jaunty Jackalope.
On Sat, Mar 07, 2009 at 02:01:31PM -0000, Peter Maydell wrote:
> > Is this issue still reproducible in Jaunty with Xfce 4.6?
>
> Presumably you have a Jaunty system; wouldn't it be better to take the
No, I don't have a jaunty system (Debian testing).
> 60 seconds to follow the instructions for reproduction in the original
> bug report (as modified to allow for the fact that the specific package
> has been removed so presumably it's some other config utility) to find
> out whether this bug is still a problem? Then you could say something
I already checked before asking, and I couldn't find the sliders you
were speaking of. Since I don't often use these dialogs, I chose not to
close the bug report directly (I could have missed them). But thanks
anyway, for trying to explain me what I should do while I'm already doing
it.
> like "The new display preferences utility in Jaunty is <foobar>; I
> checked and it doesn't have this bug." which is much more useful and
> informative and less likely to irritate bug submitters by sounding like
> a pointless health-check message; and then you would be able to actually
> close the bug...
Standard bugs responses (from <https:/ /wiki.ubuntu. com/Bugs/ Responses>
for example) are even worse that my pointless health-check message.
> (You might like to read www.chiark. greenend. org.uk/ ucgi/~cjwatson/ blosxom/ ubuntu/ 2009-02- 27 rants.html)
> http://
> -bug-triage-
These posts mostly describe interactions between bug triagers and
developers. I uploaded almost all Xfce 4.6 packages into jaunty. So,
should my developer self bash my bug triager self?
But here is the standard response I should have pasted here when closing
the bug instead of asking for input:
"
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu - the Jaunty Jackalope.
If you need a fix for the bug in previous versions of Ubuntu, please /help.ubuntu. com/community/ UbuntuBackports #request- new-packages
follow the instructions for "How to request new packages" at
https:/
"
-- /launchpad. net/~mrpouit
Lionel Le Folgoc - https:/
EEBA 555E 0CDE 92BB 3AF4 4AB3 45A0 357B 5179 5910