← Back to team overview

ubuntu-bugcontrol team mailing list archive

Re: Kubuntu triage policy conflicts with Ubuntu triage policy

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 03/29/2014 04:51 PM, Dr. David Alan Gilbert wrote:
> The reality though, is that it does make more sense to report them 
> upstream for a few reasons: 1) They tend to be up to date with
> upstream 2) Ubuntu doesn't change them. 3) There is a single
> upstream place to report them to 4) Upstream seems happy with
> taking bugs reported from Ubuntu packages.
> 
> Now that combination is rare - taking a random package it's 
> unlikely all 4 of those are true, so it doesn't make sense for it
> to be the general Ubuntu triage/report policy.

It really doesn't make sense.  Upstream is quite happy to take bug
reports as long as they also apply to the upstream package, which is
why we forward them after verifying that they do, *and* continue to
track them in Ubuntu.  Just because it also applies upstream is no
reason to to declare the bug in ubuntu to be invalid.  We track bugs
in Ubuntu so that people can find out what bugs are present, and so we
can notice when it has been fixed upstream and be sure to update or
backport the fix.

> If people were to report KDE bugs into ubuntu/lp then it's just a
> delay while someone triages it and then reports it upstream - the 
> extra comms delay doesn't help anyone.

KDE is no different in this regard than any other package in Ubuntu,
so it shouldn't have its own policy that differs from, and is not
documented in, the Ubuntu bug triaging policy.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTN04OAAoJEI5FoCIzSKrw1a8H/1GNcPFgaz63uZMXySQaWi6N
vaAqkIXogjXlDYY7T+9azw5ymQ4WrwW5GDZ/n/mk0zzFRIL823WtlsqeEMBPW77R
CfUmW8rEG9drjZYGVjmIMgxlGBVeO9rBQ1zFUvszAzYOaZNi7yKPBSz/WwnoRcgm
VyTlxF5p6gIlov6m2hGbY39tOtzB7EDoqpR6jnJaTr/1fgGsPKebklIwqngMSIqE
VeapvrAKfsUlfHawXvmqFy+ONuPV+vfIBi1GQ3x4hFewqmrUhTVo427J64AJjJez
0pd2lhUoAKEw4gYtndXzdSj7EXhbJjdRcXYsA8/Bvrkdv0+9G0hvbjgqRhK1uUQ=
=9jH3
-----END PGP SIGNATURE-----


Follow ups

References