9816 2016-06-23 13:13:47 +0000 add a RESOLVED/REPORTED UPSTREAM 2017-09-19 11:10:18 +0000 1 1 5 Infrastructure Bugzilla bugzilla unspecified x86 Multiple RESOLVED FIXED Medium normal Future 1 alex.kanavin mhalstead infras.bug.watcher Infras.watcher ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 63278 0 alex.kanavin 2016-06-23 13:13:47 +0000 When we cannot fix a bug in an upstream project, and the most we can do is to report it upstream, it would be good to have a corresponding Bugzilla resolution. None of existing resolutions are a good fit. 63295 1 ross.burton 2016-06-23 15:04:04 +0000 Next week Michael, I'll have a chat with you about this. :) 63480 2 mhalstead 2016-06-29 18:28:20 +0000 We currently have WaitForUpstream for open bugs. It sounds like we need a Resolved -> ReportedUpstream status. Will that do everything we need? 63507 3 alex.kanavin 2016-06-30 13:37:01 +0000 LGTM, but I'd like Ross to comment as well. 63508 4 ross.burton 2016-06-30 13:41:51 +0000 Yes, a RESOLVED-ReportedUpstream status would be good. I think we should then review all current WaitingForUpstream bugs and either move them to NEW (we'll fix this at some point if upstream doesn't) or RESOLVED->Reported Upstream if we're not going to put any more effort into it. As to the naming of the actual resolution, how about RESOLVED->UPSTREAM? 76919 5 alex.kanavin 2017-09-18 13:53:29 +0000 Ping? 76934 6 mhalstead 2017-09-18 17:46:42 +0000 Thank you for this ping. The new status is in place please let me know if any changes are still required. 76964 7 alex.kanavin 2017-09-19 11:10:18 +0000 Thanks, seems fine now.