| 1 |
Pacho Ramos posted on Wed, 08 Sep 2010 00:05:34 +0200 as excerpted: |
| 2 |
|
| 3 |
> El mié, 08-09-2010 a las 01:44 +0400, dev-random@××××.ru escribió: |
| 4 |
>> On Tue, Sep 07, 2010 at 09:30:34PM +0000, Robin H. Johnson wrote: |
| 5 |
>> > This implies that the upstream is alive enough to fix it. |
| 6 |
>> > |
| 7 |
>> > I feel it should mean that the bug has been reported to upstream, and |
| 8 |
>> > that state is documented in the bug. |
| 9 |
>> > |
| 10 |
>> > If we keep every upstream bug open instead of closed, we'd have |
| 11 |
>> > probably another 2500 open bugs (5312 RESO/UPSTREAM in the history of |
| 12 |
>> > Gentoo, and I'm ballparking that 50% aren't actually fixed yet |
| 13 |
>> > upstream). |
| 14 |
>> |
| 15 |
>> Bug may be a blocker. And marking it as RESOLVED/UPSTREAM you may |
| 16 |
>> unblock another bug (e.g. stabilization request) which should be still |
| 17 |
>> blocked because there is no fixed package in tree. |
| 18 |
>> |
| 19 |
>> |
| 20 |
> In most cases when it's really a blocker, bug will remain opened anyway |
| 21 |
> until solved or, if not possible, stabilization will be postponed. |
| 22 |
|
| 23 |
Additionally, RESOLVED/UPSTREAM indicates that the Gentoo package |
| 24 |
maintainer (or other dev who marked it such) believes Gentoo is not the |
| 25 |
appropriate place for a patch fixing the problem. |
| 26 |
|
| 27 |
As such, the bug will never be fixed at the Gentoo level, only upstream, |
| 28 |
and if there's a blocker on it, the blocker would never get resolved |
| 29 |
either, until upstream fixes it. Where upstream isn't active or doesn't |
| 30 |
believe the fix appropriate either, that'd lead to stalemate and forever |
| 31 |
blocking the dependent Gentoo bug. That's not appropriate either. |
| 32 |
|
| 33 |
So RESOLVED/UPSTREAM *should* unblock blockers, even where upstream |
| 34 |
doesn't resolve, or we've simply created a deadlock that's not going to be |
| 35 |
resolved. If it's truly a blocker, the problem will need worked around |
| 36 |
some other way. But often, "blockers" really aren't blockers, when |
| 37 |
upstream chooses not to take the package in that direction after all. It |
| 38 |
simply means some other alternative, perhaps an alternative package, must |
| 39 |
be developed instead, and the package as it is can continue to evolve in |
| 40 |
the normal way. |
| 41 |
|
| 42 |
-- |
| 43 |
Duncan - List replies preferred. No HTML msgs. |
| 44 |
"Every nonfree program has a lord, a master -- |
| 45 |
and if you use the program, he is your master." Richard Stallman |
Archives