Re: [PR] [FLINK-33350] Update website for release 1.18.0 [flink-web]

2023-10-26 Thread via GitHub
JingGe merged PR #691: URL: https://github.com/apache/flink-web/pull/691 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache

Re: [PR] [FLINK-33350] Update website for release 1.18.0 [flink-web]

2023-10-25 Thread via GitHub
JingGe commented on PR #691: URL: https://github.com/apache/flink-web/pull/691#issuecomment-1779181986 @snuyanzin good catch! I have addressed it. Please check it again. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [PR] [FLINK-33350] Update website for release 1.18.0 [flink-web]

2023-10-25 Thread via GitHub
PatrickRen commented on PR #691: URL: https://github.com/apache/flink-web/pull/691#issuecomment-1779109037 @snuyanzin Thanks for the reminder. Yep the [policy](https://flink.apache.org/downloads/#update-policy-for-old-releases) is that we need to release a 1.16.3 after 1.18.0, then drop sup

Re: [PR] [FLINK-33350] Update website for release 1.18.0 [flink-web]

2023-10-25 Thread via GitHub
snuyanzin commented on PR #691: URL: https://github.com/apache/flink-web/pull/691#issuecomment-1778911312 in general lgtm one question to clarify: is it ok to remove 1.16.x? I'm asking since AFAIR usually there should be 3 minor releases and the latest after the major is happen -- T

[PR] [FLINK-33350] Update website for release 1.18.0 [flink-web]

2023-10-24 Thread via GitHub
JingGe opened a new pull request, #691: URL: https://github.com/apache/flink-web/pull/691 This PR aims to update some config files related to 1.18 release. This PR is related to #680 - add announcement blog post for Flink 1.18 -- This is an automated message from the Apache Git Serv