why not simply marking it as 'unscheduled'? IMO that pretty much expresses that this is is not yet scheduled but still considered a valid improvement/bug that we want to address at some point.
i only resolve issues 'later' or 'wontfix' that i am confident that will never be fixed. adding a 'wish list' fix version will just be another huge container that we hardly ever look at and i would find it hard to understand the difference between 'unscheduled' and 'wish list'. if something is on your wishlist, i would suggest you assign the issue to yourself in order to keep track of it (compared to the whole bunch of other unscheduled issues). or flag it with a label that allows you to find all your wishes. so, rather -1 from my side. kind regards angela On 29/07/15 08:58, "Stefan Egli" <[email protected]> wrote: >Hi, > >Just came across a ticket [0] that has no urgent priority to be fixed in >1.3 >but would be a good candidate to be put into the general 'wish list pod'. > >Now currently we seem to handle such cases by just closing the ticket. >This >imv has the downside of it getting completely lost and forgotten. > >We could thus introduce a new 'wish list' fix version that can be set on >those tickets instead of just closing them. > >Wdyt? > >Cheers, >Stefan >-- >https://issues.apache.org/jira/browse/OAK-2613 > >
