Towards Apache Apex 3.6.0 release

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=

[jira] [Closed] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay M Pujare closed APEXCORE-561. Resolution: Won't Do This is no longer needed and will use the timeline server as suggeste

[jira] [Reopened] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay M Pujare reopened APEXCORE-561: -- Need to be closed with correct type > Container info needs to be persisted even after app

[jira] [Resolved] (APEXCORE-493) Purge the checkpoints from the containers

[ https://issues.apache.org/jira/browse/APEXCORE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-493. - Resolution: Won't Do > Purge the checkpoints from the containers > -

[jira] [Resolved] (APEXCORE-683) Apex client should support application packages on HDFS

[ https://issues.apache.org/jira/browse/APEXCORE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-683. - Resolution: Implemented Fix Version/s: 3.6.0 > Apex client should support application pac

[jira] [Updated] (APEXCORE-678) Shutdown of application should start from input nodes

[ https://issues.apache.org/jira/browse/APEXCORE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar Gosavi updated APEXCORE-678: --- Fix Version/s: 3.6.0 > Shutdown of application should start from input nodes > -

[GitHub] apex-core pull request #500: Apexcore 550.better error message on java versi...

Github user oliverwnk closed the pull request at: https://github.com/apache/apex-core/pull/500 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature i

[jira] [Created] (APEXCORE-700) Make the plugin registration interface uniform

Pramod Immaneni created APEXCORE-700: Summary: Make the plugin registration interface uniform Key: APEXCORE-700 URL: https://issues.apache.org/jira/browse/APEXCORE-700 Project: Apache Apex Core

[jira] [Assigned] (APEXCORE-699) Investigate versioning for plugins

[ https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-699: Assignee: Tushar Gosavi > Investigate versioning for plugins > --

[jira] [Created] (APEXCORE-699) Investigate versioning for plugins

Pramod Immaneni created APEXCORE-699: Summary: Investigate versioning for plugins Key: APEXCORE-699 URL: https://issues.apache.org/jira/browse/APEXCORE-699 Project: Apache Apex Core Issue

[jira] [Resolved] (APEXCORE-456) Explicitly limit Server.Subscriber to one way communication

[ https://issues.apache.org/jira/browse/APEXCORE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-456. - Resolution: Fixed Fix Version/s: 3.6.0 > Explicitly limit Server.Subscriber to one way co

[jira] [Updated] (APEXCORE-660) Documentation for Control tuple support changes

[ https://issues.apache.org/jira/browse/APEXCORE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-660: Fix Version/s: (was: 3.6.0) > Documentation for Control tuple support changes > --