Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Feel free to join on Google Meet. Local dial-in numbers can be found at https://tel.meet/wcx-fjbt-hhz?pin=1940846765126

Timeline

  • Feature Freeze
    • January, 17th of 2023, end of business CEST.

...

Chinese new year is 22 January: 1+ week holiday. Ppl will be back in early FebruaryRelease
Mid of March 2023

Highlight features

please feel free to add/suggest.

...

symbolmeaningcomment
(big grin)validatedthrough cross team testing
(tick)donewell documented with a complete test coverage
(green star)will make itthere is no reason this effort should not go into 1.17
(star)in dangerthere are some concerns the effort could be ready for the feature freeze of 1.17
(red star)very unlikelythere are severe concerns the effort could make it to 1.17
(minus)won't make itit was decided against adding this for the 1.17 release. working on the effort has been stopped.
(question)state unclear
(blue star)independentas the artefact artifact could be released independent of Apache Flink

...

Numbers are based on the items in the list below, not on the tickets 

110753031

(big grin)(tick) (green star) (star)(red star)(minus)(question)(blue star)Remaining weeks
2022-11-01








13
2022-11-15








11
2022-11-29
410000230379
2022-12-13
72410190427
2022-12-27
72510180425
2023-01-22023-01-1010
92700350443
2023-01-17
13230

List

0332442
2023-01-24
162100332451
2023-01-31
265001600470
2023-02-145233






List

Feel Feel free to add categories.

Runtime
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
Shuffle

Jira
serverASF JIRA

columnIdsissuekey,summary

serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29801



FLIP in voting(minus)




Shuffle









Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29766

Xintong Song 
(tick)


(big grin)100%10-01-2023
Adaptive Batch Scheduler supports hybrid shuffle modeWeijie Guo Xintong Song (minus)
10-01-202314-02-2023

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

30469

30938

AdaptiveBatchScheduler should supports early consumption for dynamic graph.Weijie Guo
Yuxin Tan
 Xintong Song 
(green star)50%


(minus)




Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30469

Yuxin Tan Xintong Song 

(tick)100%17-01-202317
09
-01-202310-02-2023self-test
Further improvement of production availability of hybrid shuffle

(big grin)
(green star)50%
100%17-01-202317
10
-01-2023
self-test
Deployment & Cluster Coordination
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
REST API

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-27060




(big grin)
(tick)
100%
15
20-
11
02-
2022
202315-11-202215-11-2022self-test

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30583


The first stage is finished, and the second stage is improvement, it will be finished in the next version.(tick)100%09-01-202305-01-202309-01-2023
Reactive Mode
n/a
Scheduler

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29663

(green star)


(tick) 
80%
100%
03
17-01-2022
FLIP-281: Speculative execution for sink



Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30725

Biao Liu 
FLIP in discussion(green star)30%


(tick) 100%31
03
-01-2022
FLIP-283: Use adaptive batch scheduler as default scheduler for batch jobsFLIP in discussion(green star)30%


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-31005

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30682



(tick) 100%31
03
-01-2023


Misc
n/a
OLAP
n/a
State backend
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified

FLIP-263: Improve resolving schema compatibility

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29844

Hangxiang Yu 
(green star)


(minus)80%
10
31-1-2023


Improve File Management in State Backend


(green star)




(minus)5%
13
31-
12
1-
2022
2023


Improve the serializer performace of state change of changelog

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30345

(green star)


(big grin)100%
10
31-1-2023

self-test

Allow to configure Changelog Storage per program

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-26372

(green star)


(minus)70%
10
31-1-2023


Add a metric for back-pressure from the ChangelogStateBackend

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-24402

(green star)


(minus)40%
13
31-
12
1-
2022
2023


Frocksdb cannot run on Apple M1

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-24932

(green star)


(big grin)
90%
100%
13
30-
12
1-
2022CheckpointName/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verifiedBenchmark Generic Incremental CP + UC + BDYuan Mei (question) JiraserverASF JIRA
2023

Tested  by Martijn Visser 

Release FRocksDB 6.20.3-ververica-2.0

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

26803

30836

Rui Fan
Piotr Nowojski
(green star)70%10-12-2022


(big grin)100%31-1-2023

Tested by Martijn Visser 

Checkpoint
Benchmark
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
Improve benchmark stability
Benchmark Generic Incremental CP + UC + BDYuan Mei 

(minus)




Jira
serverASF JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId5aa69414-a9e9-3523-82ec-879b028fb15bkeyFLINK-29825Yuan Mei (green star)50%3-1-2023

serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-26803



(tick)100%

 




Benchmark
API JiraserverASF JIRA










Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified

Improve benchmark stability

Jira
serverASF JIRA

serverId5aa69414-a9e9-3523-82ec-879b028fb15bkeyFLINK-29740Deprecated(tick)100%08-11-202208-11-202208-11-2022

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

28641

29825

Martijn Visser
Removed
Yuan Mei 
(green star)


(minus)
40%
50%
08-11-2022
31-1-2023


API
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

24456(question)

29740


Deprecated
(big grin)100%08-11-202208-11-202208-11-2022Self-tested

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

18647

28641


Removed
(minus)40%31-01-2023


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-24456

Dawid Wysakowicz 


(green star)90%31-01-2022


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-18647


FLIP DiscussionNeed to be postponed to the next release(minus)
10-01-2023


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29668

Martijn Visser 
Removed
(tick)

(big grin)100%14-11-202214-11-202214-11-2022Self-tested

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30050

(question)





(big grin)90%31-01-2022

Self-tested

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-25509

Hang Ruan Coding






SQL
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
General

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29942

Godfrey He ,@Yunhong Zheng

(green star)



(tick)
70%
100%2023-01-
10
31


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-28016

(green star)



(minus)
31-01-2023


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29281

Chesnay Schepler 
(green star)



(minus)
31-01-2023


Table API
Calcite Update

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

20873

30025




(minus)
2023-01-20


Calcite Update

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-20873




(tick)




Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-21239




(tick)




Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29932

Sergey Nuyanzin 
(green star)



(tick)
31-01-2023


Flink Dialect

ALTER TABLE API

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-21634

(green star)



(big grin)
90%
100%2023-
01Hive Dialect
02-
10DELETE/UPDATE API (FLIP-282) voting(green star)2023-01-10
14

self-tested

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

29635

30648


(green star)60%




(big grin)100%2023-02-14

self-tested
Hive Dialect

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

29717

29635

(green star)80%



(tick)



Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-30951

2023-01-10

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

26603

29717

luoyuxia



(tick)
(question)
100%2023-01-31
SQL Gateway



Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

29941

26603

Shengkai Fang
, Zelin Yu

(green star)2023



(minus)
70%

31-01-
10
2022
QEFLIP-280: Introduce a new explain mode to provide SQL advicevoting(green star)2023-01-10QO

Image RemovedFLINK-27591 - Improve the plan for batch queries when statistics is unavailable OPEN

Godfrey He ,@Yunhong Zheng

(green star)40%API/PythonName/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified Jira



SQL Gateway

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29941

Shengkai Fang  , Zelin Yu



writing doc(green star)100%2023-01-10

Jira

serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

29155HuangXingbo (tick)100%10-01-2023

30936

QE

Jira
serverASF JIRA

serverId5aa69414-a9e9-3523-82ec-879b028fb15bkeyFLINK-29833HuangXingbo (minus)0%10-01-2023

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

JiraserverASF JIRA

serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

28957

30650

HuangXingbo
(green star)



(big grin)
70%
100%
10
2023-01-
2023
10

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

29421

31025

HuangXingbo (green star)0%10-01-2023
QO

Image AddedFLINK-27591 - Improve the plan for batch queries when statistics is unavailable OPEN

Godfrey He ,@Yunhong Zheng




Need to be postponed to the next release(minus)40%2023-1-31


API/Python

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-21223

HuangXingbo (tick)100%10-01-2023Machine Learning
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
CEPName/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verifiedWebName/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29155

HuangXingbo 


(tick)100%10-01-2023

self-test

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29833

HuangXingbo 


(minus)0%10-01-2023


Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

29995(question)

Status / Follow-ups

2022-11-01

Agenda

...

28957

HuangXingbo 


(tick)100%19-01-2023

self-test

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29421

HuangXingbo 


(tick)100%19-01-2023

self-test

...

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-

...

21223

HuangXingbo 


(tick)100%10-01-2023

self-test
Machine Learning
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
n/a
CEP
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
n/a
Web
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified

2022-11-15

Agenda

...

  • Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyFLINK-29387
  • Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyFLINK-29315
  • Jira
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyFLINK-29818

...

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-29995



(tick)100%



Status / Follow-ups

2022-11-01

Agenda

  • Kickoff
  • Keeping the state of features updated (ideally before the sync)
  • Blockers
      -18356
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-
      29899
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-26674
    • 24119
  • Build stability
  • Are there any (new) contributors who need a PR reviewed or merged? And if yes, who can help out?

2022-11-

...

15

Agenda

  • Kickoff
  • Keeping the state of features updated (ideally before the sync)
  • Blockers

...

  • Build instabilities
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-28766
      : Anton has some new findings on that issue and will get back on it
      29387
    • Pulsar-related issues:
      Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-
      29835
      29315
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-
      29755
      29818
  • Build stability
    • Number of growing test stability issues with "Exit code 137 errors"
      • Jiraserver
        Jira
        server
        ASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-
        29836
      Python-related issues:
      • 18356
      • Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-29461
        Matthias Pohl pings Xingbo Huang / Dian Fu 
        29899
      • Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-26974-26674
  • Are there any (new) contributors who need a PR reviewed or merged? And if yes, who can help out?

2022-11-29

  • Build instabilities
    • Jira
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-18356
      : OOM errors are most likely being caused by flink-table-planner (Godfrey He might be a person to reach out to about it)
      28766
      : Anton has some new findings on that issue and will get back on it
    • Pulsar-related issues:
      • Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-
      29427: Qingsheng Ren will look into the PR
      • 29835
      • Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-
      27916 Matthias Pohl will ping contributors on the issue - but it's not that urgent since it's not failing that frequently 
  • Other topics:
    • Externalizing Pulsar connector (test instabilities): Martijn Visser  is working on externalizing the code base
    • Performance test monitoring: Discussion is happening on the mailing list
    • Externalizing connectors in general is work-in-progress but looks good
    • Public CI documentation can be improved

2022-12-13

...

      • 29755
      • Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-29836
    • Python-related issues:
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-

      ...

          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-

      ...

          • 26974
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-18356

      ...

        • : OOM errors are most likely being caused by flink-table-planner (Godfrey He might be a person to reach out to about it)
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-

      ...

        • 29427
          : Qingsheng Ren will look into the PR
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK

      ...

      2022-12-27

      ...

        • -27916
          Matthias Pohl will ping contributors on the issue - but it's not that urgent since it's not failing that frequently 
      • Other topics:
        • Externalizing Pulsar connector (test instabilities): Martijn Visser  is working on externalizing the code base
        • Performance test monitoring: Discussion is happening on the mailing list
        • Externalizing connectors in general is work-in-progress but looks good
        • Public CI documentation can be improved

      2022-12-13

      ...

      • Build instabilities
        • Jira
        • serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-

      ...

        • 29405
          → Qingsheng to have a look at the PR
        • Pulsar connector has been synced to external connector repository. Martijn Visser to open a PR to remove connector from master

      2023-01-10

      ...

        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-18356
          → Qingsheng to ping Godfrey
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-

      ...

        • 18356
          → The PR is still failing for the same issue as this PR should fix. We should ping the author to have a look first
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-

      ...

      • Blocker: New test instabilities which were introduced in unreleased versions only
      • Critical: New test instabilities that also affect released versions; Test instabilities that pop up more than two times per month (because they affect CI maintenance)
      • Major: Test instabilities that popped up after the version was released but happen rarely
        • 27916
          → Martijn to ping Thomas once more
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-26974
          → Xingbo is working on this
      • How to have monitoring and quality control for the externalized connectors → Need to have a discussion on the Dev mailing list. Martijn Visser to make a proposal and open a discussion thread on this topic.

      2022-12-27

      • Meeting skipped due to Christmas holiday/sick leaves
      • Discussion started on moving the feature freeze from Jan 17 to Jan 31 due to pandemic situation in China (see dev ML discussion thread)
      • Pulsar connector has been externalized. Pulsar-related test instabilities were disabled in release-1.16  and release-1.15  (see
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-30351
        and parent task)

      2023-01-10

      • Build instabilities (all 1.17 test instabilities with a priority >=Major)
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-18356

          • Godfrey He and Yunhong Zheng are working on it
          • run tests after each other/not in parallel
          • don't reuse JVMs
          • JUnit has feature to log memory consumption
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-26974
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-29427
      • Priorities of test instabilities (docs about it)
        • Test instabilities are prioritized as Critical and become blocker as soon as we notice that they are newly introduced
      • Feature freeze extended until Jan 31, 2023
      • Switching to weekly calls as we're getting closer to the feature freeze?
        • Yes, switch to weekly will happen. Next meeting will be Jan 17 due to Chinese New Year coming up and the feature freeze happening soon  
      • Votes on FLIPs are stalled due to outstanding votes
      • leader elections lacks test coverage (FLIP-285,
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-26522
        )
        • No issues popped up on the mailing list since 1.16

      2023-01-17

      • Build instabilities (all 1.17 test instabilities with a priority >=Major)
        • Blockers
          • Performance regressions
            • Jira
              serverASF JIRA
              serverId5aa69414-a9e9-3523-82ec-879b028fb15b
              keyFLINK-30623
              → In progress
            • Jira
              serverASF JIRA
              serverId5aa69414-a9e9-3523-82ec-879b028fb15b
              keyFLINK-30625
              → In progress
            • Jira
              serverASF JIRA
              serverId5aa69414-a9e9-3523-82ec-879b028fb15b
              keyFLINK-30624
              → In progress
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-29405
            → Qingsheng will look into this one after FLINK-29427 (see below)
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-29427
            → Qingsheng currently is looking into this 
        • Martijn Visser to check open critical test stabilities to determine if some need to be assigned / if we're OK in the overall direction
        • FLIP-272: Generalized delegation token support has been merged in and a blog post will be written and published about it, prior to the 1.17 release
        • https://github.com/apache/flink/pull/21606 has been merged into Flink, but should also be taken into account for externalized connectors - This is tracked under
          Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-30639

      2023-01-24


      • Build instabilities (all 1.17 test instabilities with a priority >=Major)
        • Performance regressions
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30623
            → In progress
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30625
            → In progress
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30624
            → In progress
        • Blockers
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-29405
            → In progress, needs a status update
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30727
            → In progress, needs a status update
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30328
            → Resolved
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-29427
            → In progress, needs a status update
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-30618
          Martijn Visser is looking into this one
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-30733
          Martijn Visser is looking into this one

      2023-01-31

      • Today is feature freeze day
      • 26 features / improvements are in for Flink 1.17 (47 in at Flink 1.16, 20 for Flink 1.15, 27 for Flink 1.14)
        • 5 features are still listed as expected to be completed, but are not yet in, 4 of them have been merged and are writing documentation,  Martijn Visser to check/update for the status of these items. 
      • Blockers:
          • Jira
            serverASF JIRA
            columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution
            columnskey,summary,type,created,updated,due,assignee,reporter,Priority,Priority,Priority,Priority,priority,status,resolution
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30881
            Matthias will look into this 
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-29427
            → Leonard review PASS, waiting CI green
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-29405
            → Fixed by Qingsheng
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30625
            → Should be resolved, pending validation by the benchmarks (related to FLINK-30624). Benchmarks look to be improved, downgraded to Critical. 
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30624
            → Should be resolved, pending validation by the benchmarks (related to FLINK-30625). Benchmarks look to be improved, downgraded to Critical. 
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30623
            → Martijn to reach out to Dong, Rui Fan, Piotr. We're planning to give them until Friday the 3rd of February to come to a conclusion on this ticket; if no consensus is achieved, then the original commit that introduced the regression should be reverted. 
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30826
            → Matthias to check if this has already been resolved via another ticket (multiple related tickets)
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30727
            →  [Critical]  PR to update buffers for the test has been merged, will be continued to monitor. Test downgraded to Critical
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30846
             [Critical]  Downgraded to Critical as it's only a test-related issue and doesn't indicate a bug in production.
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30844
            →  [Major] Test downgraded to Major, If the test fail again contributor will increase the waiting interval for this test as a solution.
          • Jira
            serverASF JIRA
            columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution
            columnskey,summary,type,created,updated,due,assignee,reporter,Priority,Priority,Priority,Priority,priority,status,resolution
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-30870
            →  [Major]  Leonard downgrade the issue priority to Major as it's a known slack plugin issue
      • Martijn Visser to communicate to the Flink community this evening that the feature freeze has started and we plan to cut the release branch at the end of this week (Friday 3rd of February). 

      2023-02-07

      • master  is stabilized enough to cut the release-1.17  branch
        • FLINK-30921 - The Azure apt mirror instabilities seem to have been resolved for now. 
        • FLINK-30908 - The issue turned out to be a problem that existed in previous releases
      • Release branch is going to be cut today by Leonard Xu 
      • Release testing will be announced: 2 weeks will be planned for this

      2023-02-14

      • Status update on release testing efforts
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-30926
        • End of cross-team testing date is 21st of February 2023. We will monitor the status throughout the week and hopefully conclude everything next week. 
        • When a feature is cross-team tested, the icon needs to be changed from (tick) to (big grin) to indicate that the testing has been completed
        • We always look for volunteers: picking up a cross-team testing task is much appreciated. 
      • Proposal: Create Jira issues for release management tasks to document what was done to improve review-ability (alternatively, add expected output to release documentation)
        • Do this from now on for the next steps in release management (create release candidate etc.)
      • Test instabilities:
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31036
          : Blocker 
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-18356
          : Starts failing more regularly again. Qingsheng Ren to ping Godfrey He and Yunhong Zheng 
        • FLINK-30972 (openssl version update necessary) continues to fail because ofFLINK-30965 (repo-sync doesn't pick up 1.15 changes anymore)

      2023-02-21

      • Open Blocker issues
      • Example Release Jira issues:
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-31146
         >
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-31154
      • Release testing not finished, yet
      • Decision on RC creation moved to next week's Flink release sync call
      • Other issues:
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31133
          : Issue in 1.15.3 unexplained
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31092
          : 1.17 issue in Hive
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-30733
          : no updates on the Slack bot instability so far
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31134
          : OOM issue - waiting for Gabor's response
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31145
          (Kafka infrastructure umbrella ticket)

      2023-02-28

      • Blockers: are these really blockers or do we want to move the release forward?
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31092
           → Qingsheng Ren to check the status with Shengkai Fang 
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31104
          Qingsheng Ren to check the status with Shengkai Fang 
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-30978
           → Qingsheng Ren to check the status with Shengkai Fang 
      • Other issues:
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31134
          : Revisit OOM in Kafka e2e test in 1.15.3 - we're keeping it as critical for now. There are no other artifacts that we can investigate. The test doesn't involve table-runner code (therefore, isn't connected to
          Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-18356
          ). → Martijn Visser to check internally
        • Dependabot alerts are affecting all commiters now
      • Release managers to review draft of 1.17 announcement
      • Release 1.17 preparation:
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-31146

      2023-03-07

      • Ubuntu mirror instabilities: 
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-30921
        Matthias Pohl will follow-up on that one
      • API backwards compatibility:
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-31167
        Do we have additional documentation on API compatibility? Leonard Xu will do another pass over the ticket comments to confirm the findings
      • Announcement: FLIPs missing: FLIP-272: Generalized delegation token support, FLIP-217: Support watermark alignment of source splits Leonard Xu reaches out to contributors to add something related to the announcement
      • Instabilities (blocker query):
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31351
          :Leonard Xu has pinged luoyuxia  to look into this issue. 
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31278
          : Downgraded→  [Critical] PR ready, flink-runtime tests will be made sequential ,
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31339
          : Downgraded→  [CriticalLeonard Xu has pinged Godfrey He to look into this issue.
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31342
          : Downgraded→  [Critical
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31341
          : Downgraded→  [Critical
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31354
          :  Downgraded→  [Critical] Matthias Pohl 
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31355
          : Downgraded→  [Critical]  Leonard Xu has pinged Dian Fu to look into this issue. 

      2023-03-14

      • Flink RC2 for 1.17 is available, needs checkers (smile)

      2023-03-21

      2023-03-23

      • Flink 1.17.0 is officially released today!

      Retrospective:

      From Qingsheng Ren 

      • As discussed in the mailing list, we need to trigger a final patch version for 1.15 after releasing 1.17. Some cleanup steps need to be reviewed and changed, such as removing 1.15 data from svn, CI, flink-docker etc. See
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-31570
      • I like the idea made by Matthias Pohl that we track TODOs for releasing on JIRA 👍 I used it as a checklist to make sure we don't miss anything. Also it helps collaborating, as we can divide works across RMs easily by assigning JIRA tickets.

      From Matthias Pohl 

      • Google Meet might not be the best choice for the release sync. We need to be able to invite attendees even if the creator of the meeting isn't available (maybe try Zoom or even Jitsi as an OpenSource alternative instead?)

      • Release sync every 2 weeks and a switch to weekly after feature freeze felt reasonable
      • Slack worked well as a collaboration tool to document the monitoring tasks (#builds, #flink-dev-benchmarks) in a team with multiple release managers

      • The Slack Azure Pipeline bot seems to be buggy. It swallows some build failures. It's not a severe issue, though. We created #builds-debug to monitor whether it's happening consistently. The issue is covered in

        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-30733

      • We experienced occasional issues in the manual steps of the release creation in the past (e.g. japicmp config was not properly pushed). Creating Jira issues for the release helped to make the release creation more transparent and made the steps more reviewable. Additionally, it helped to distribute subtasks to different people with Jira being the tool for documentation and synchronization. That's especially helpful when there is more than one person in charge of creating the release.

        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31146
        • RCs
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-31154
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-31578
          • Jira
            serverASF JIRA
            serverId5aa69414-a9e9-3523-82ec-879b028fb15b
            keyFLINK-31583
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31562
        • Jira
          serverASF JIRA
          serverId5aa69414-a9e9-3523-82ec-879b028fb15b
          keyFLINK-31567
      • We had backports/merges without PRs happening by committers occasionally during the 1.17 release which broke master/release branches (probably, changes were done locally before merging which were not part of the PR to have a faster backport experience). It might make sense to remind everyone that this should be avoided. Not sure whether we want/can restrict that.

      • We observed a good response on fixing test instabilities by the end of the release cycle but had some long running issues earlier in the cycle which caused extra efforts on the release managers due to reoccurring test failures.

      • Release testing picked up “slowly”: Initially, we planned 2 weeks for release testing. But there was not really any progress (tickets being created and worked on) in the first week. In the end, we had to extend the phase by another week resulting in 3 instead of 2 weeks of release testing. I guess we could encourage the community to create release testing tasks earlier and label them properly to be able to monitor the effort. That would even enable us to do release testing for a certain feature after the feature is done and not necessarily only at the end of the release cycle.

      • Manual test data generation is tedious (
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-31593
        ). But this should be fixed in 1.18 with
        Jira
        serverASF JIRA
        serverId5aa69414-a9e9-3523-82ec-879b028fb15b
        keyFLINK-27518
        being almost done.
      • We started creating documentation for release management. The goal is to collect what tasks are there to help support a Flink release to encourage newcomers to pick up the task.

      From Leonard Xu 

      • We can keep RC0 (a non-votable one) in future releases, as an initial version for developers to validate, so that some issues could be found earlier and avoid repeatedly canceling and re-creating RCs. 

      From Martijn Visser 

      • We should be more careful for commits without a PR / green CI, which brought some problem at the end of 1.17 release cycle. There might not be possible to totally ban this, but we could give an reminder to committers. 

      ...