getup | hello, when a bug has been marked as verification-done, how long does it generally take to become available in the stable repo's? | 10:21 |
---|---|---|
rbasak | getup: normally there's a minimum ageing period of 7 days. After that it goes into the updates pocket as soon as an SRU team member gets round to reviewing it. Normally within a (further) week. | 10:34 |
rbasak | getup: ageing starts as soon as the package is accepted into the proposed pocket. | 10:34 |
getup | rbasak: that's fast, thanks for your answer | 10:35 |
teward | rbasak: i've seen it expedited from -proposed -> -updates, is that only done in cases of, say, crit level bugs? | 14:19 |
rbasak | teward: or where it doesn't make sense. | 14:19 |
rbasak | (to wait) | 14:19 |
rbasak | tzdata for example | 14:19 |
teward | mmm | 14:20 |
teward | rbasak: stupid question unrelated: if bcmwl has a crit level bug, what's triage steps for it? (wrt yesterday's email from Alberto on the bugcontrol list) | 14:20 |
teward | other than marking it triaged and setting the importance? | 14:20 |
teward | last i've seen we as nonprivileged (that is to say, non-Canonical, non-Restricted-Access people) can't actually upstream it anywhere | 14:21 |
teward | bdmurray: ^ in case you want the final overall rule on that. | 14:21 |
teward | (did I mention that i avoid driver bugs like the plague though... :/) | 14:24 |
=== txspud` is now known as txspud | ||
rbasak | teward: AIUI, it's fine for a bug to be triaged and then just sit there. Trying to progress it is separate to the bug status. | 14:28 |
=== pgraner is now known as pgraner-afk | ||
=== pgraner-afk is now known as pgraner | ||
=== emma_ is now known as emma |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!