>I retriggered the Nightly(beta) GitHub Action and have got the green result.
>https://github.com/apache/flink/actions/runs/27113488068

great, thanks

On Thu, Jun 11, 2026 at 10:34 AM Zhu Zhu <[email protected]> wrote:
>
> +1 (binding)
>
> - verified checksum and signature
> - built from sources
> - the website pr looks good
>
> Thanks,
> Zhu
>
> Yunfeng Zhou <[email protected]> 于2026年6月10日周三 13:34写道:
>
> > Hi Sergey,
> >
> > I retriggered the Nightly(beta) GitHub Action and have got the green
> > result.
> > https://github.com/apache/flink/actions/runs/27113488068
> >
> > I’ll also try to reach out to people who might be familiar with the Azure
> > environment to see if it could be fixed.
> >
> > Best regards,
> > Yunfeng
> >
> > > 2026年6月10日 00:45,Sergey Nuyanzin <[email protected]> 写道:
> > >
> > > I created a jira issue for that more than a month ago [1].
> > > However if I remember correctly, only people from Ververica and Alibaba
> > > have access to this environment and can fix it if we are talking about
> > > Azure.
> > >
> > > Another option: have green nightly in GHA
> > >
> > > [1] https://issues.apache.org/jira/browse/FLINK-39497
> > > Best regards,
> > > Sergey
> > >
> > > On Tue, Jun 9, 2026, 15:49 Martijn Visser <[email protected]>
> > wrote:
> > >
> > >> It does look that for Azure it's not picking up the latest commits
> > >> from release-1.20, the cron there is still running builds from
> > >> November last year.
> > >>
> > >> Op di 9 jun 2026 om 12:58 schreef Sergey Nuyanzin <[email protected]
> > >:
> > >>
> > >>>
> > >>> Gha or Azure
> > >>> In case of 1.20.4 gha was green
> > >>>
> > >>> Best regards,
> > >>> Sergey
> > >>>
> > >>> On Tue, Jun 9, 2026, 12:24 Yunfeng Zhou <[email protected]>
> > >> wrote:
> > >>>
> > >>>> Hi Sergey,
> > >>>>
> > >>>> Does the "nightly green” means the Azure nightly pipeline for
> > >> flink-mirror?
> > >>>> https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1
> > >>>>
> > >>>> This pipeline does have failed for branch release-1.20, but it is
> > >> based on
> > >>>> a commit more than half a year ago. Flink-mirror has stopped
> > >> synchronizing
> > >>>> this branch. The guideline “Creating a Flink Release” also does not
> > >> mark
> > >>>> this pipeline as a blocker to verify before proposing a release
> > >> candidate.
> > >>>>
> > >>>> Apart from this pipeline, the Github Actions have all passed for the
> > >>>> current release candidate, as can be seen in the commit history page.
> > >>>> https://github.com/apache/flink/commits/release-1.20.5-rc2
> > >>>>
> > >>>> So I thought the verification for this branch should be enough to
> > >> start a
> > >>>> vote.
> > >>>>
> > >>>> Best regards,
> > >>>> Yunfeng
> > >>>>
> > >>>>> 2026年6月9日 15:05,Sergey Nuyanzin <[email protected]> 写道:
> > >>>>>
> > >>>>> Should not we have at least one green nightly before starting the
> > >> vote?
> > >>>>>
> > >>>>> Best regards,
> > >>>>> Sergey
> > >>>>>
> > >>>>> On Tue, Jun 9, 2026, 08:55 Dian Fu <[email protected]> wrote:
> > >>>>>
> > >>>>>> +1 (binding)
> > >>>>>>
> > >>>>>> - verified checksum and signature
> > >>>>>> - the website PR LGTM
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> Dian
> > >>>>>> On Tue, Jun 9, 2026 at 10:11 AM Xintong Song <[email protected]
> > >>>
> > >>>>>> wrote:
> > >>>>>>>
> > >>>>>>> +1 (binding)
> > >>>>>>>
> > >>>>>>> - verified checksum and signature
> > >>>>>>> - verified source distribution contains no binary
> > >>>>>>> - verified build from source
> > >>>>>>> - tried a few examples jobs on a standalone cluster
> > >>>>>>>
> > >>>>>>> Best,
> > >>>>>>>
> > >>>>>>> Xintong
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> On Mon, Jun 8, 2026 at 7:42 PM Yunfeng Zhou <
> > >>>> [email protected]
> > >>>>>>>
> > >>>>>>> wrote:
> > >>>>>>>
> > >>>>>>>> Hi everyone,
> > >>>>>>>> Please review and vote on the release candidate #2 for the version
> > >>>>>>>> 1.20.5, 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 2EC0 F1E8 2EA8 72E3 0FE4  EDEE 7C83 478D 4985
> > >> D451
> > >>>>>>>> [3],
> > >>>>>>>> * all artifacts to be deployed to the Maven Central Repository
> > >> [4],
> > >>>>>>>> * source code tag "release-1.20.5-rc2" [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.
> > >>>>>>>>
> > >>>>>>>> Thanks,
> > >>>>>>>> Yunfeng
> > >>>>>>>>
> > >>>>>>>> [1]
> > >>>>>>>>
> > >>>>>>
> > >>>>
> > >>
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12356854&projectId=12315522
> > >>>>>>>> [2]
> > >> https://dist.apache.org/repos/dist/dev/flink/flink-1.20.5-rc2/
> > >>>>>>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > >>>>>>>> [4]
> > >>>>>>>>
> > >>>>>>
> > >> https://repository.apache.org/content/repositories/orgapacheflink-1923/
> > >>>>>>>> [5]
> > >> https://github.com/apache/flink/releases/tag/release-1.20.5-rc2
> > >>>>>>>> [6] https://github.com/apache/flink-web/pull/855
> > >>>>>>
> > >>>>
> > >>>>
> > >>
> >
> >



-- 
Best regards,
Sergey

Reply via email to