I've found two JS files in the source distribution that lack the license
header:

  - flink-runtime-web/web-dashboard/.eslintrc.js
  - flink-runtime-web/web-dashboard/.stylelintrc.js

On Wed, Jun 3, 2026 at 3:27 PM Sergey Nuyanzin <[email protected]> wrote:

> Thanks for driving the release
> seems I had to vote as
> -1 (binding)
>
> based on Nexus[1]
> it is built with jdk17 while it should be built with jdk11
>
>
> [1] https://repository.apache.org/#stagingRepositories
>
> On Tue, Jun 2, 2026 at 8:57 PM Yuepeng Pan <[email protected]> wrote:
> >
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version
> > 2.3.0, 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 B5B638DCA5F94E4A [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-2.3.0-rc2" [5],
> > * website pull request listing the new release and adding announcement
> > blog post [6],
> > * flink pull request adding release note for users [7].
> >
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> >
> > Thanks,
> > Yuepeng Pan
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12356392&projectId=12315522
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-2.3.0-rc2/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1918
> > [5] https://github.com/apache/flink/tree/release-2.3.0-rc2
> > [6] https://github.com/apache/flink-web/pull/853
> > [7] https://github.com/apache/flink/pull/28123
>
>
>
> --
> Best regards,
> Sergey
>

Reply via email to