ubuntu-bugcontrol team mailing list archive

[C de-Avillez <hggdh2@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/10/14 03:03, Alberto Salvia Novella wrote:
> ∅:
>> In the even of a failure in debian-installer, for example, the
>> apport tools are not available and being that it is not 
>> necessarily a crash, it makes it hard to report. What files
>> should we request?
> 
> I think only a software developer could tell just in time, so I
> would mark the bug as triaged if it had already the following
> information: - How to reproduce - Expected behaviour - Real
> behaviour - Ubuntu release - Package version
> 
> 
> ∅:
>> https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1380774
>
>> 
> - Instead of mentioning the test-case number, I would rather put
> the link to it. - Instead of writing all along, I would rather
> broke the description into sections: how to reproduce, expected
> behaviour, real behaviour. And put the technical information at the
> end.
> 
> But it's okay.
> 
> 
> ∅:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363180
> 
> Except for the missing capitals and comas, it's all right :-P
> 
> 
> ∅: 
> https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1376380
> 
> You forgot to add the bug-watch to the panel!
> 
> 
> ∅: https://bugs.launchpad.net/ubuntu/+source/obconf/+bug/1272834
> 
> There's some duplicated information in the description.
> 
> 
> ∅: 
> https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1216788
>
>  Just in case you need to know for the future, it's safer to set
> the bug status to incomplete. Then ask the user, if the bug is
> still affecting a supported release, to enter the name of this
> release into the tag list and set the bug status back to its
> previous set.
> 
> 
> I see there's still a bit need of proficiency. On the other hand I
> feel that where you failed isn't a matter of you had to practise
> more before applying, but the triaging manual being obscure on
> these regards.
> 
> So I agree with you joining the team: thank you.

@ ∅:

Except you did not state how you would set up importance on these bugs.

Please state them.

..C..

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUPnOkAAoJECWAD5grd+mNcykP/19me/aAsHbK0QBk/6ZuE6GA
zmZ+asda8f2uEsZkrp5i0z/mN1XoXcDADB8RnV1LP4I0v+R3ucdnJPE2dPbx8Qal
NPWErHjTuEIWAy5buLj3EmCdCWbSXzyV0kJSkbXFtaE11qkgyNUkqKX3hhv/sTV2
Smd9DudlDkd/HvNnr6f3rWgGt/KTLrorzx9cxl69+WQHa5Q9/fdmneEZx3H6H77S
XYczR/RpDU0pPOC6Zp7FhOACOkOkhtq0yCGgHb0T0tRhiON8+Xgxcy7RxR9BWdNz
UDm7JZQbgllPnf261YA55bg9xUE0LeuvOqosAHKqM0VOHZOpaUHdPEQFb14ikyr+
DcsA9odaJZo6FyF2jqYta4CSPVusG2BcV2vgFkAKttK97uRjRuTB1oXGQrfTmvMv
/hmeEYQC7RVbUf5H3NrHopKS70aJGJblZDLXjjIcjpu1SM/KoYivLj6AunGX4e6G
ixQja6ZSXZnvS1G3fHjzUZFBTX6WI9ZOhg1f9IOMJqwWRW7JGEC2rO038LZWOx1L
nD/WnEWaUgDg1tC6yRk/crsfbnfDxeflQC7iIMnprWa0SUYhOkZ5azfz01g2+/9L
fjz+XKxdvjcA3vXhnIUVIDhoPlW3jnWMk6QPIEIvSn14PwRRylKW0gt1/ilxHLtd
ggMIgUOp6NrHCQ5jrXDL
=MXSK
-----END PGP SIGNATURE-----