Hi, APEXCORE-641 has been fixed and I marked it resolved. I have moved my PR which I believe may result in a minor improvement from the blocking path.
Thanks On Mon, Apr 24, 2017 at 12:24 PM, Tushar Gosavi <tus...@datatorrent.com> wrote: > Hi All, > > I am going to cut first RC in few days. There are two JIRA pending > APEXCORE-700 and APEXCORE-641. APEXCORE-700 is close to merge. @Vlad, Can > we move APEXCORE-641 out of 3.6? > > List of 3.6 issues. > https://issues.apache.org/jira/browse/APEXCORE/fixforversion > /12338818/?selectedTab=com.atlassian.jira.jira-projects-plug > in:version-issues-panel > > Thanks, > - Tushar > > > On Fri, Apr 14, 2017 at 9:16 PM, Dean Lockgaard <dean.lockga...@gmail.com> > wrote: > > > Vlad, > > > > Here is my thought process about these tickets. Both 692 (Apex dev setup > > sandbox section to reference Apex website downloads page) and 687 (update > > supported Hadoop v2.6 in Apex docs) are Apex documentation issues, and so > > they are part of the Apex release process. Furthermore, 692 directly > > references 693 (update Apex website downloads page with cleaned up and > > augmented list of 3rd party binaries), so it makes sense to have 693 > > updated as well, though of course I agree that it is not a part of Apex > > core release nor a blocker for the release. > > > > Thanks, > > Dean > > > > > > > > On Fri, Apr 14, 2017 at 11:27 AM, Vlad Rozov <v.ro...@datatorrent.com> > > wrote: > > > > > Dean, > > > > > > 692 and 693 are web site documentation issues and are not part of the > > Apex > > > core 3.6.0 release. 687 can be covered in the release README (known > > issues). > > > > > > Thank you, > > > > > > Vlad > > > > > > On 4/13/17 14:11, Dean Lockgaard wrote: > > > > > >> I'd like to request that 687, 692 and 693 be included in the 3.6.0 > > >> release. I will send PRs for these shortly. > > >> > > >> Thanks, > > >> Dean > > >> > > >> > > >> > > >> On Fri, Apr 14, 2017 at 5:05 AM, Amol Kekre <a...@datatorrent.com> > > wrote: > > >> > > >> +1 to cut a release > > >>> > > >>> Thks > > >>> Amol > > >>> > > >>> > > >>> E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre* > > >>> > > >>> www.datatorrent.com > > >>> > > >>> > > >>> On Thu, Apr 13, 2017 at 9:22 AM, Pramod Immaneni < > > pra...@datatorrent.com > > >>> > > > >>> wrote: > > >>> > > >>> +1 > > >>>> > > >>>> I would like to see 699 and 700 addressed as well. > > >>>> > > >>>> On Wed, Apr 12, 2017 at 10:16 PM, Tushar Gosavi < > > tus...@datatorrent.com > > >>>> > > > >>>> wrote: > > >>>> > > >>>> Hi, > > >>>>> > > >>>>> It has been four month since 3.5.0 Apex Core release. There are > > several > > >>>>> > > >>>> new > > >>>> > > >>>>> features added to core after 3.5.0. I would like to propose the > 3.6.0 > > >>>>> release of Apex Core, to make these features available to users. > > >>>>> > > >>>>> The list of issues fixed in 3.6.0 are: > > >>>>> https://issues.apache.org/jira/issues/?jql=project%20% > > >>>>> 3D%20APEXCORE%20AND%20status%20in%20(Resolved%2C%20Closed)% > > >>>>> 20AND%20fixVersion%20%3D%203.6.0%20ORDER%20BY%20status%20ASC > > >>>>> > > >>>>> Apart from above JIRAs, which bug-fixes/features people will like > to > > >>>>> > > >>>> see > > >>> > > >>>> in > > >>>> > > >>>>> this release. If you feel your JIRA should be included then please > > set > > >>>>> > > >>>> fix > > >>>> > > >>>>> version to 3.6.0 with estimated time for work completion, also > > discuss > > >>>>> > > >>>> it > > >>> > > >>>> here. Some of the pending pull requests could be incorporated in the > > >>>>> release. I feel following JIRA should be part of release > > APEXCORE-649, > > >>>>> APEXCORE-678. > > >>>>> > > >>>>> Let me know about your thoughts. > > >>>>> > > >>>>> Thanks, > > >>>>> Tushar. > > >>>>> > > >>>>> > > > > > >
