Great! Thanks a lot for the information, Thejas. --Xuefu
On Thu, May 28, 2015 at 10:17 AM, Thejas Nair <thejas.n...@gmail.com> wrote: > Once you update it, I think you should sync with Sushanth and get it > included in the branch-1.2 RELEASE_NOTES.txt file. That way a 1.2.1 > would have it right. > > > > On Thu, May 28, 2015 at 10:16 AM, Thejas Nair <thejas.n...@gmail.com> > wrote: > > Yes, there is a way to do bulk updates to jira, if you have admin > > privileges in Jira (which you should have). > > Once you search for issues in jira with a criteria, in the search > > result page, you will see a drop down under tools in top right side of > > the page. That has a bulk update option. > > > > Yes, I think we should update the fix version of jiras in a branch, as > > soon as the merge happens. Otherwise its hard to figure out what > > release has the fixes. > > > > > > On Thu, May 28, 2015 at 9:21 AM, Xuefu Zhang <xzh...@cloudera.com> > wrote: > >> Hi all, > >> > >> When I check Hive 1.2.0 release notes > >> < > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329345&styleName=Text&projectId=12310843 > >, > >> I found that the JIRA list missed many Hive on spark related JIRAs that > >> were resolved in HIVE 1.2. I guess the problem is that the fix version > of > >> these JIRAs weren't updated when they are merged to trunk. Partly my > bad, > >> but this is probably a general issue happening at the time merging. > Thus, > >> I'm wondering if there is a way to bulk update these JIRAs when they are > >> merged. > >> > >> Thanks, > >> Xuefu >
