-1

Build failed for the following exception:
[image: 企业微信截图_ccae150e-a072-4426-90c0-92cba5098464.png]

The source package does not have a git directory.

Best wishes,
Charles Zhang
from Apache InLong


Verne Deng <[email protected]> 于2025年5月12日周一 10:10写道:

> Hello Apache InLong PMC and Community,
>
>     This is a call for a vote to release Apache InLong version 2.2.0-RC0.
>
>     The tag to be voted on is 2.2.0-RC0:
>
>     https://github.com/apache/inlong/tree/2.2.0-RC0
>
>     The release tarball, signature, and checksums can be found at:
>
>     https://dist.apache.org/repos/dist/dev/inlong/2.2.0-RC0/
>
>     Maven artifacts are available in a staging repository at:
>
>
> https://repository.apache.org/content/repositories/orgapacheinlong-1509
>
>     Artifacts were signed with the
> 266E0074EA51139EBA8C0375433463746F28A521 key, which can be found in:
>
>     https://downloads.apache.org/inlong/KEYS
>
>     2.2.0 includes ~ 87 bug fixes and improvements done since the last
> versions, which can be found at:
>
>     https://github.com/apache/inlong/blob/2.2.0-RC0/CHANGES.md
>
>     Please download, verify, and test.
>
>     The VOTE will remain open for at least 72 hours.
>
>     [ ] +1 Release this package as Apache InLong 2.2.0
>     [ ] +0
>     [ ] -1 Do not release this package because...
>
>     To learn more about Apache InLong, please see
>     http://inlong.apache.org/
>
>     Checklist for reference:
>
>       [ ] Download links are valid.
>       [ ] Checksums and signatures.
>       [ ] LICENSE/NOTICE files exist
>       [ ] No unexpected binary files
>       [ ] All source files have ASF headers
>       [ ] Can compile from source
>       [ ] All Tests Passed
>
>       More detailed checklist, please refer to the following:
>       https://inlong.apache.org/community/how-to-verify
>
> Thanks,
> Your InLong Release Manager
>

Reply via email to