> However, if the release version was assigned properly, the > release manager or component owners would have no choice but to do the > review.
There is actually an alternative the release managers tend to follow. They simply move all the unresolved tickets to the next version blindly. This happens around a release day and I get a dozen of JIRA notifications saying that a ticket assigned to version X was rescheduled to version Y. Anyway, we cannot force a single contributor such as the release manager to be responsible for this. This should be a collaborative process established between Ignite committers. However, regardless of the chosen process those who are going to asses new tickets have to look them up first. And here is a rule of “setting a ticket to the latest version” might be one of the best options. — Denis > On Nov 7, 2017, at 2:57 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > On Wed, Nov 8, 2017 at 6:06 AM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > >> Dima, >> >> As I already mentioned, the whole community more or less followed this >> process for years already with no success. My suggestion is to ask >> component maintainers to perform regular review of relevant tickets. >> > > Your suggestion will not work, because we cannot force anyone to do the > tickets review. However, if the release version was assigned properly, the > release manager or component owners would have no choice but to do the > review. > > To counter your point, I think we had much more success reviewing the > tickets before, when we had mainly assigned all the tickets to the upcoming > release, than now. > > D.
