Notice: moving fix version of unresolved issues to 1.11.0/1.10.1

2020-02-09 Thread Yu Li
Hi All, Since we're about to release 1.10.0 (the vote of RC3 [1] is in good shape although still not concluded), we plan to change fix version of the unresolved issues to 1.11.0/1.10.1. We will start from issues with "Open" status, and then the "In-Progress" ones. Any con

Re: Fix version

2016-03-04 Thread Greg Hogan
Hi Max, You are right, there is no need to unlabel old fix versions. My thought was to treat the fix version like "inbox zero". There is already an emphasis on closing blockers, but few bugs and fewer features are that severe. Pull requests can be long lived and require a ready

Re: Fix version

2016-03-01 Thread Maximilian Michels
Hi Greg, I agree that we should encourage people to use the "fix version" field more carefully. I think we need to agree on how we use "fix version". How about going through the existing "fix version" tagged issues instead of just removing the tag? I do think th

Re: Fix version

2016-02-25 Thread Robert Metzger
Hi Greg, I agree with you that the "fix version" field for unresolved issues is probably used by issue creators to express their wish for fast resolution. I also saw some cases where issues were reopened. I agree with your suggestion to clear the "fix version" field once 1.0

Fix version

2016-02-22 Thread Greg Hogan
Hi, With 1.0.0 imminent there are 112 tickets with a "fix version" of 1.0.0, the earliest from 2014. From the ticket logs it looks like we typically bump the fix version once the target release has passed. Would it be better to wait to assign a fix version until achieving some comb