When to mark a bug as STAGED

[Josh DuBois]

I was recently looking at bug 18070 in relation to a problem I had 
installing Office 2010:

https://bugs.winehq.org/show_bug.cgi?id=18070

The last comment asks whether the bug can be marked STAGED.  In talking 
with Sebastian he questioned whether it would make sense in this case, 
because the patch in the staging tree which improves behavior is clearly 
a hack as opposed to something which is progress toward a more permanent 
solution.

To me it made sense to go ahead and mark the bug as STAGED anyhow, to 
record the fact that one of the patches in the stating tree addresses 
the behavior.  Perhaps this is one way to help associate patchsets with 
bugs so that we can tell the motivation for a particular patchset in 
staging.  (In this case, a URL on the bug also has information about the 
motivation, here: https://dev.wine-staging.com/patches/132/ ).

So the question: If a staging patchset is more along the lines of a 
dead-end hack than it is progress toward a long-term solution, should 
bugs which are fixed by the patchset still be marked STAGED?

My gut differed from Sebastian's, so I thought it best to ask here to 
reach a consensus.

(I can see the value either way - just looking for a standard approach.)