Thanks, Joo Yeon! It's actually better not to set fix version automatically, since we don't know when we'll resolve a particular issue.
-Gon On Fri, Nov 23, 2018 at 3:31 PM Joo Yeon Kim <jooy...@apache.org> wrote: > Thanks for the quick response John. > > Since this is the very first release, I'll see how things go. > I'm also investigating the new power in Nemo JIRA, trying to see if there > is an automatic assignment to fields (ex. automatically setting fix version > to 0.2 when creating issues after the first release.) > > I'll wait for the others now. > > Cheers, > Joo Yeon > > On Fri, Nov 23, 2018 at 3:24 PM John Yang <johnya...@gmail.com> wrote: > > > Thanks Joo Yeon! > > > > I've set the fix versions for the issues I've reported as per your > > suggestion. There is quite a lot of them! > > > > This is how I did it. Hope it is useful for others doing the same. > > - I've used this query in the JIRA to filter the issues > > reporter = johnyangk AND project="Apache Nemo" AND status = Resolved > > - Some of the issues were marked 'Resolved' but the Resolution was 'Won't > > fix"(or Invalid, etc), which means that the issue was not addressed with > a > > PR but was just closed. I've decided not to mark fix version for those > > issues. > > - For the others, I've marked the fix version one by one. > > - Only one of my issues was resolved after Nov.20 > > > > Since there is a lot of resolved issues reported by a number of different > > committers, and it appears that only the issue reporter has the access to > > mark fix version, I suppose it is important for everyone to check their > > issues and set fix versions appropriately. > > > > However, some committers may not be active in the community at the > moment, > > or may miss this thread. We may need a way to deal with issues reported > by > > those folks, if necessary. > > > > Cheers, > > John > > > -- Byung-Gon Chun
