Thanks Ashutosh, this is much clearer. I'll update JIRA Guidelines <https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-JIRAGuidelines> .
-- Lefty On Wed, Nov 4, 2015 at 2:56 PM, Thejas Nair <[email protected]> wrote: > the problem with setting fix version before commit is that it is error > prone, ie wrong fix version remains there. It is better to make a > conscious decision about fix version once it is committed. > > > On Wed, Nov 4, 2015 at 11:39 AM, Sergey Shelukhin > <[email protected]> wrote: > > Given that target version is only useful before commit and the fix > version > > only after commit, I wonder if we need two fields... > > > > On 15/11/4, 10:56, "Ashutosh Chauhan" <[email protected]> wrote: > > > >>Historically there has always been a confusion about Fix Version. To > >>reduce > >>that confusion, I requested asf infra to add target version field for > >>Hive > >>jira and they promptly added that. So, now we have an additional target > >>version for jira tickets. If you are creating new ticket, it will show up > >>on "Create" screen. If you want to add the field on previously created > >>jira, just hit "edit" button and it will show up. > >> > >>Just to reiterate purpose of two fields: > >> > >>Fix Version : Earliest version on which patch for that jira has landed. > It > >>should be updated *after* commit has been made. > >>Target Version : Earliest version on which you are aiming to land the > >>patch. It should be updated *before* commit has been made. > >> > >>Thanks, > >>Ashutosh > > >
