+1

I have checked:

[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
[x] All files have license headers if necessary.
[x] No compiled archives bundled in source archive.

---
Best Regards,

Chufeng (Eric) Gao

On Sun, Feb 5, 2023 at 5:09 PM 李进勇 <[email protected]> wrote:
>
> Hello DolphinScheduler Community,
>
> This is a call for vote to release Apache DolphinScheduler version 2.0.8
> round3. thx
>
> Currently, our community is preparing to release version 2.0.8, which will
> only do bugfix without new features.
>
> Release notes: https://github.com/apache/dolphinscheduler/releases/tag/2.0.8
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/dolphinscheduler/2.0.8/
>
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1147/org/apache/dolphinscheduler/
>
> Git tag for the release:
> https://github.com/apache/dolphinscheduler/tree/2.0.8
>
> Release Commit ID:
> https://github.com/apache/dolphinscheduler/commit/2a22b960580c907f67128a294df2b10b4380312a
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/dolphinscheduler/KEYS
>
> Look at here for how to verify this release candidate:
> https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/contribute/release.md
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code artifacts have correct names matching the current release.
> [ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
>
> ------
> Best Wish
> — JinYong Li

Reply via email to