[jira] [Created] (FLINK-10349) Unify stopActor* utils

[JIRA]

陈梓立 created FLINK-10349:
---

 Summary: Unify stopActor* utils
 Key: FLINK-10349
 URL: https://issues.apache.org/jira/browse/FLINK-10349
 Project: Flink
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.7.0
Reporter: 陈梓立
Assignee: 陈梓立
 Fix For: 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10350) Add assignTimestampsAndWatermarks in KeyedStream

[Jiayi Liao (JIRA)]

Jiayi Liao created FLINK-10350:
--

 Summary: Add assignTimestampsAndWatermarks in KeyedStream
 Key: FLINK-10350
 URL: https://issues.apache.org/jira/browse/FLINK-10350
 Project: Flink
  Issue Type: New Feature
Reporter: Jiayi Liao






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[VOTE] Release 1.5.4, release candidate #1

[Till Rohrmann]

Hi everyone,
Please review and vote on the release candidate #1 for the version 1.5.4,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key
with fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.4-rc1" [5],
* website pull request listing the new release and adding announcement
blog post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12343899
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.5.4/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1181
[5] https://github.com/apache/flink/tree/release-1.5.4-rc1
[6] https://github.com/apache/flink-web/pull/123

Cheers,
Till

Pro-tip: you can create a settings.xml file with these contents:



  flink-1.6.0


  
flink-1.6.0

  
flink-1.6.0


https://repository.apache.org/content/repositories/orgapacheflink-1181/


  
  
archetype


https://repository.apache.org/content/repositories/orgapacheflink-1181/


  

  



And reference that in your maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

[VOTE] Release 1.6.1, release candidate #1

[Till Rohrmann]

Hi everyone,
Please review and vote on the release candidate #1 for the version 1.6.1,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key
with fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.6.1-rc1" [5],
* website pull request listing the new release and adding announcement
blog post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12343752
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.1/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1180
[5] https://github.com/apache/flink/tree/release-1.6.1-rc1
[6] https://github.com/apache/flink-web/pull/124

Cheers,
Till

Pro-tip: you can create a settings.xml file with these contents:



  flink-1.6.0


  
flink-1.6.0

  
flink-1.6.0


https://repository.apache.org/content/repositories/orgapacheflink-1180/


  
  
archetype


https://repository.apache.org/content/repositories/orgapacheflink-1180/


  

  



And reference that in your maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.