Is that possible to configure to set "Fix Version² to ³trunk" if nothing is specified when one resolve the JIRA. I guess most of time we commit to trunk.
Puru. On 10/9/14, 1:00 PM, "Rohini Palaniswamy" <[email protected]> wrote: >Folks, > I also see lot of jiras resolved without marking "Fix Version". Please >update the correct Fix Version for the jiras in the first page of > >https://issues.apache.org/jira/issues/?jql=project%20%3D%20Oozie%20AND%20r >esolution%20%3D%20Fixed%20AND%20fixVersion%20is%20EMPTY%20ORDER%20BY%20upd >ated%20DESC > >to either 4.1.0 or trunk. > >Regards, >Rohini > >On Thu, Oct 9, 2014 at 12:54 PM, Purshotam Shah < >[email protected]> wrote: > >> I have checkin https://issues.apache.org/jira/browse/OOZIE-2023 >>yesterday >> night. >> Pending JIRA is https://issues.apache.org/jira/browse/OOZIE-1896. I >>should >> be able to resolve it by tomorrow night. >> >> Puru >> >> >> >> On 10/9/14, 12:30 PM, "Rohini Palaniswamy" <[email protected]> >> wrote: >> >> >Puru/Ryota, >> > I see a lot of HA related important bugs not checked into 4.1 and >>with >> >HA being one of the major release themes we need to have those in 4.1. >> >Can >> >you ensure by tomorrow that you have them all checked in? And there >>seems >> >to be issues with the PreCommit build as well with tests getting Killed >> >half way through. We need to get that resolved as well. >> > >> >Regards, >> >Rohini >> > >> >On Thu, Oct 9, 2014 at 11:53 AM, Rohini Palaniswamy >> ><[email protected] >> >> wrote: >> > >> >> Bowen, >> >> Please look at all issues and determine if they are blockers for the >> >> release in terms of functionality or major issues. Just because no >>one >> >>is >> >> working on them now, does not mean we can make a release with major >> >>issues. >> >> >> >> Regards, >> >> Rohini >> >> >> >> >> >> On Tue, Oct 7, 2014 at 5:30 PM, Robert Kanter <[email protected]> >> >> wrote: >> >> >> >>> ah, ok. Then can you change the versions on the other JIRAs to be >> >>>trunk? >> >>> >> >>> On Tue, Oct 7, 2014 at 5:13 PM, bowen zhang >><[email protected]> >> >>> wrote: >> >>> >> >>> > Excluding my blocker of publishing oozie artifacts, we agreed in a >> >>> > previous email a couple weeks ago that anything with no patch or >> >>>active >> >>> > development will not be considered for 4.1 once the deadline is >> >>>passed. >> >>> > >> >>> > ------------------------------ >> >>> > *From:* Robert Kanter <[email protected]> >> >>> > *To:* "[email protected]" <[email protected]>; bowen zhang < >> >>> > [email protected]> >> >>> > *Sent:* Tuesday, October 7, 2014 2:32 PM >> >>> > *Subject:* Re: OOZIE-2023 and 4.1 release >> >>> > >> >>> > Are you sure that's the remaining task? >> >>> > >> >>> > I see 7 tasks currently targeting the 4.1 release: >> >>> > http://s.apache.org/oozie4.1 >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > On Tue, Oct 7, 2014 at 1:41 PM, bowen zhang < >> >>> > [email protected]> wrote: >> >>> > >> >>> > Hi Purshotam, >> >>> > [OOZIE-2023] Job rerun can stuck in prep - ASF JIRA this is the >> >>> remaining >> >>> > task we need to get it done for 4.1 release. Do you have latest >> >>>update >> >>> on >> >>> > this? It's in patch available state. >> >>> > Thanks, >> >>> > Bowen >> >>> > >> >>> > >> >>> > >> >>> > [OOZIE-2023] Job rerun can stuck in prep - ASF JIRA >> >>> > Job rerun is divided into two commands. 1. ReRunXCommand, which >> >>>delete >> >>> > action and set job status to prep. 2. StartXCommand, which start >>WF. >> >>> > View on issues.apache.org Preview by Yahoo >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> >> >> >> >> >> >>
