Hi devs and users,

Yesterday was the first release sync of Flink 1.19, I’d like to share the
summary:

- Sync meeting
We switched back to google meet because there's some account limitation for
zoom on some region and the google meet is available when creator is not
online.
The meeting will happen every 2 weeks and switch to weekly after the
feature freeze.

- Feature freezing date
Jan 26, 2024

- Features & issues tracking
The community has collected many features on the 1.19 wiki page[1] and it
is encouraged to continuously updating the page for contributors, also
there exists large amounts of jira issues[2].
Please be aware that, for all `@Public` APIs that are intended to be
changed / removed in release 2.0, the deprecation work should be completed
in 1.19.
Another important thing is that since a lot of the work in 1.19 is also
related to the 2.0 release, tagging related issues with '2.0-related' tag
will make it easier for the 2.0 release managers to track progress.

- Daily work divisions
In general, every release manager will be working on all daily issues. For
some major tasks, in order to make sure there will at least always be
someone to take care of them, they have been assigned to specific release
managers[1]. If you need support in each of these areas, please don't
hesitate to contact us.

- Blockers
  - FLINK-31449 Remove DeclarativeSlotManager related logic @Xintong will
track it
  - FLINK-33531 Nightly Python fails @Dian Fu will look at this
  - FLINK-18356 flink-table-planner Exit code 137 on ci pipeline @Matthias
pr reviewing

- Retrospective of 1.18 release
Thanks for the efforts from previous release managers and also several
valuable thoughts and suggestions:
  - The release process now has a jira template, which will make the work
easier for the new release managers, and the overall steps will still
documented on the wiki page and continuously updated in the next releases.
We'll also be looking at automation to continue to streamline releases.
  - 1.18 experienced relatively long release testing, We found that finding
volunteers to join the testing after rc is ready can be a long wait. So in
1.19 we will try to find volunteers earlier(we added a new column:
volunteers for testing on the wiki page[1]), and before release testing,
let the feature developers describe the detailed testing steps, so that
subsequent testing can go faster.
  - The documentation build and flink-docker CI have been migrated to
GHA(Github actions), there's still a lot of work to be done to migrate the
CI pipeline from azure to GHA[3], and welcome to join in for our goal of
improving the experience of our contributors!

The next release sync will be on November 28th, 2023.

Google Meet: https://meet.google.com/vcx-arzs-trv

[1] https://cwiki.apache.org/confluence/display/FLINK/1.19+Release
[2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=592
[3] https://issues.apache.org/jira/browse/FLINK-27075

Best regards,
Yun, Jing, Martijn and Lincoln

回复