Andrey, You're right about a misunderstanding between `closed` and `resolved` issues. This statuses also are not completely clear for me. My point here is keeping an issue `PA` or `Open` is safer to a release manager rather than resolving such issues.
Also, my personal understanding of 2.8.1 release is a bugfix release, so we should not include `improvements` to it. The goal for them should be 2.9. I think we will discuss all these things right after 2.8 will be announced. On Wed, 11 Mar 2020 at 17:51, Andrey Gura <ag...@apache.org> wrote: > > Maxim, > > the key word here is *closed*, not *resolved*. In such terms we can > resolve issue but it won't mean that issue is included in some release > until it will not be closed. > > Unfortunately we have many not closed but released issues. > > On Wed, Mar 11, 2020 at 4:33 PM Maxim Muzafarov <mmu...@apache.org> wrote: > > > > Folks, > > > > > > I think we can close an issue with specific `fixVersion` value only > > after related to the issue PR has been merged to the corresponding > > `fixVersion` branch. In the other case, we just lose such an issue in > > the `fixVersion` release branch, so it's better to avoid doing that > > [1]. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12756 > > > > On Wed, 11 Mar 2020 at 05:01, Ivan Pavlukhin <vololo...@gmail.com> wrote: > > > > > > Andrey, > > > > > > > targeting to specific version means that this change should be > > > > included in release with target fix version. No more, no less. > > > > > > What do you mean by "targeting to a specific version" here? Fix > > > version in JIRA? Something else? > > > > > > My main point here is to simplify things. Issues like [1] looks > > > invalid for me. And I expect problems from such issues in the future. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12756 > > > > > > Best regards, > > > Ivan Pavlukhin > > > > > > ср, 11 мар. 2020 г. в 03:23, Andrey Gura <ag...@apache.org>: > > > > > > > > Ivan, > > > > > > > > targeting to specific version means that this change should be > > > > included in release with target fix version. No more, no less. > > > > > > > > On Wed, Mar 11, 2020 at 2:42 AM Ivan Pavlukhin <vololo...@gmail.com> > > > > wrote: > > > > > > > > > > Igniters, > > > > > > > > > > Initially I wanted to delay the discussion about everything related to > > > > > 2.8.1 until all 2.8 release activities are finished, but I already see > > > > > some possible problems. Mainly it is related to adding tickets to > > > > > 2.8.1 scope. I recall that it was already discussed in some other > > > > > thread that it is not good idea to mark tickets with 2.8.1 fix version > > > > > because a branch for it does not exist yet and technically we can > > > > > resolve tickets for 2.9 but not for 2.8.1. > > > > > > > > > > I checked JIRA for 2.8.1 and found a bunch of tickets with 2.8.1 fix > > > > > version [1] and what is even worse some of them are already RESOLVED > > > > > [2]. > > > > > > > > > > Not using 2.8.1 looks much cleaner especially for RESOLVED tickets. > > > > > But I feel that we can miss some tickets because an intent to include > > > > > a ticket into 2.8.1 is not indicated at all. > > > > > > > > > > Please share your thoughts how the situation could be improved. > > > > > > > > > > [1] > > > > > https://issues.apache.org/jira/browse/IGNITE-12769?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.8.1 > > > > > [2] > > > > > https://issues.apache.org/jira/browse/IGNITE-12756?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.8.1%20AND%20resolution%20is%20not%20EMPTY%20 > > > > > > > > > > Best regards, > > > > > Ivan Pavlukhin
