+1, Thanks Xianjing Feng

Jie Yang

roryqi <ror...@apache.org> 于2023年12月6日周三 18:44写道:

> +1 binding
> I checked. Download links, checksums and PGP signatures are valid. Source
> code distributions have correct names matching the current release. Release
> files have the word incubating in their name. DISCLAIMER-WIP, LICENSE and
> NOTICE files are correct. Tests passed. I run `mvn package`
>
> Xianjing Feng <xianjingf...@apache.org> 于2023年12月4日周一 21:39写道:
>
> > Hello Uniffle Community,
> >
> > This is a call for vote to release Apache Uniffle (Incubating) version
> > 0.8.0-rc3.
> >
> > Release notes:
> > https://uniffle.apache.org/download/release-notes-0.8.0
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.8.0-rc3/
> >
> > The Staging Repository:
> >
> https://repository.apache.org/content/repositories/orgapacheuniffle-1002/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-uniffle/tree/v0.8.0-rc3
> >
> > Keys to verify the Release Candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS
> >
> > GPG user ID:
> > xianjingfeng
> >
> > As the DISCLAIMER-WIP shows, this release still left some license
> > problems, which will be gradually resolved during incubation.
> >
> > 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 distributions have correct names matching the current
> > release.
> > [] LICENSE and NOTICE files are correct for each LUniffle repo.
> > [] All files have license headers if necessary.
> > [] No unlicensed compiled archives bundled in source archive.
> >
> > More detail checklist please refer:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Thanks,
> > xianjingfeng
> >
>

Reply via email to