[jira] [Updated] (FLINK-3957) Breaking changes for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-3957: Labels: 2.0-related auto-deprioritized-major (was: auto-deprioritized-major) > Breaking changes for Flink 2.0 > -- > > Key: FLINK-3957 > URL: https://issues.apache.org/jira/browse/FLINK-3957 > Project: Flink > Issue Type: New Feature > Components: API / DataSet, API / DataStream, Build System >Affects Versions: 1.0.0 >Reporter: Robert Metzger >Priority: Minor > Labels: 2.0-related, auto-deprioritized-major > Fix For: 2.0.0 > > > From time to time, we find APIs in Flink (1.x.y) marked as stable, even > though we would like to change them at some point. > This JIRA is to track all planned breaking API changes. > I would suggest to add subtasks to this one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-3957) Breaking changes for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-3957: -- Labels: auto-deprioritized-major (was: stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Breaking changes for Flink 2.0 > -- > > Key: FLINK-3957 > URL: https://issues.apache.org/jira/browse/FLINK-3957 > Project: Flink > Issue Type: New Feature > Components: API / DataSet, API / DataStream, Build System >Affects Versions: 1.0.0 >Reporter: Robert Metzger >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 2.0.0 > > > From time to time, we find APIs in Flink (1.x.y) marked as stable, even > though we would like to change them at some point. > This JIRA is to track all planned breaking API changes. > I would suggest to add subtasks to this one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-3957) Breaking changes for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-3957: -- Labels: stale-major (was: ) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Breaking changes for Flink 2.0 > -- > > Key: FLINK-3957 > URL: https://issues.apache.org/jira/browse/FLINK-3957 > Project: Flink > Issue Type: New Feature > Components: API / DataSet, API / DataStream, Build System >Affects Versions: 1.0.0 >Reporter: Robert Metzger >Priority: Major > Labels: stale-major > Fix For: 2.0.0 > > > From time to time, we find APIs in Flink (1.x.y) marked as stable, even > though we would like to change them at some point. > This JIRA is to track all planned breaking API changes. > I would suggest to add subtasks to this one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-3957) Breaking changes for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-3957: -- Summary: Breaking changes for Flink 2.0 (was: Breaking API changes for Flink 2.0) > Breaking changes for Flink 2.0 > -- > > Key: FLINK-3957 > URL: https://issues.apache.org/jira/browse/FLINK-3957 > Project: Flink > Issue Type: New Feature > Components: Build System, DataSet API, DataStream API >Affects Versions: 1.0.0 >Reporter: Robert Metzger > Fix For: 2.0.0 > > > From time to time, we find APIs in Flink (1.x.y) marked as stable, even > though we would like to change them at some point. > This JIRA is to track all planned breaking API changes. > I would suggest to add subtasks to this one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
