I think if we are pretty sure that the issue will be fixed in a version, it is better to be labeled as the specific version. If we are not sure, it is better to label it as "backlog".
>From external user side, it is much better since they will know when the issues they are watching will be fixed. Cheers Lei On Fri, Dec 23, 2016 at 9:02 AM, Vineet Goel <[email protected]> wrote: > Agree with Ruilong. > > And for JIRA owners, please remember to update the Fix Version when you > close a JIRA. There are many JIRAs which are resolved/closed but Fix > Version = Backlog, which is very confusing for a someone looking to see > which release has the fix. > > > On Thu, Dec 22, 2016 at 4:52 PM Ruilong Huo <[email protected]> wrote: > > > As these issues are not resolved, I think it is more reasonable to mark > the > > affected version as 2.1.0.0-incubating and make fix version as backlog. > > Then the correct fix version can be marked at the time when the issue is > > actually resolved. > > > > Best regards, > > Ruilong Huo > > > > On Fri, Dec 23, 2016 at 8:24 AM, Lei Chang <[email protected]> wrote: > > > > > Sounds a good idea! > > > > > > Cheers > > > Lei > > > > > > > > > On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <[email protected]> wrote: > > > > > > > We have a significant number of JIRAs opened and currently with a fix > > > > version of 2.1.0.0-incubating. As this is a source only release, I am > > > > inclined to start the branch/tagging release process and update these > > > JIRAs > > > > with the next release version (2.2.0.0-incubating currently > available). > > > > Thoughts? > > > > > > > > HAWQ 2.1.0.0-incubating (Open, In Progress, Reopened) > > > > https://issues.apache.org/jira/browse/HAWQ-1232?filter=12339113 > > > > > > > > Thanks, > > > > -=e > > > > > > > > FYI: Although we may change the version for the next release, I am > > using > > > > this as a place holder for the next release JIRAs. > > > > > > > > -- > > > > *Ed Espino* > > > > *[email protected] <[email protected]>* > > > > > > > > > >
