Subject: Re: [boost] Trac policy on "won't fix" issue
From: Robert Ramey (ramey_at_[hidden])
Date: 2009-05-26 12:52:18
I've got a couple of those.
What I really need is an option "can't fix". Since I don't have that
I use "won't fix". About half the time, the original poster
reopens it because he thinks I should fix it anyway. At this
point I just leave it open and move on.
Vladimir Prus wrote:
> Suppose there's an issue in Trac about program_options library. The
> is such that I personally have no hope of *ever* fixing it. What
> should be
> done to such issue:
> 1. Close it as won't fix.
> 2. Keep it open.
> (1) has the advantage that the issue won't show up in my searched,
> life easier for me, but it reduces chances that somebody else will
> accidentally see and fix it. OTOH, the chances of such fix are also
> pretty low.
> So, I personally prefer (1), but I also think we should have a single
> consistent meaning of what open issue in Trac means, and under what
> cases an issue that is not actually fixed can be closed.
> Any comments?
> - Volodya
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk