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
