Agree. No need to just keep reassigning a whole bulk of tickets from one release to another.
D. On Tue, Jan 5, 2016 at 2:23 AM, Yakov Zhdanov <[email protected]> wrote: > Guys, > > Our current Jira process involves going through potentially 100s of tickets > and moving them from one release to another. On top of being time > consuming, it just seems plain redundant. > > I think a much better approach would be for the committers and contributors > to keep the tickets assigned to themselves between releases, and whenever > they feel that the feature will make a certain release, set the > “fixVersion” in the ticket. > > The above process would work for the majority of bug fixes. Of course we > would still separately monitor tickets associated with main release > features and schedule them properly on the Release Plan [1] page. > > Comments? > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Plan > > --Yakov >
