The Jira ticket is CELEBORN-941. I fixed it yesterday but I didn't
realize that merge_pr.sh failed to copy it into branch-0.3.

Regards,
Ethan

Cheng Pan <[email protected]> 于2023年9月1日周五 15:39写道:
>
> Ethan, could you please create the corresponding JIRA ticket(s) and set the 
> priority to blocker?
>
> Thanks,
> Cheng Pan
>
>
> > On Sep 1, 2023, at 15:33, Ethan Feng <[email protected]> wrote:
> >
> > -1(bingding)
> > The deploy doc in this RC needs to be updated.
> >
> > Regards,
> > Ethan
> >
> > 在 2023年9月1日星期五,Mridul Muralidharan <[email protected]> 写道:
> >
> >> +1
> >>
> >> Signatures, digests, license, etc check out fine.
> >> Checked out tag and build/tested with -Pspark-3.1
> >>
> >> Regards,
> >> Mridul
> >>
> >>
> >> On Thu, Aug 31, 2023 at 11:35 AM Cheng Pan <[email protected]> wrote:
> >>
> >>> Hi Celeborn community,
> >>>
> >>> This is a call for a vote to release Apache Celeborn (Incubating)
> >>> 0.3.1-incubating-rc0
> >>>
> >>> The git tag to be voted upon:
> >>>
> >>> https://github.com/apache/incubator-celeborn/releases/tag/
> >> v0.3.1-incubating-rc0
> >>>
> >>> The git commit hash:
> >>> b3992274e207959125d8784d9b61a6e8043612fc source and binary artifacts
> >> can be
> >>> found at:
> >>>
> >>> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0
> >> .3.1-incubating-rc0
> >>>
> >>> The staging repo:
> >>> https://repository.apache.org/content/repositories/orgapache
> >> celeborn-1037
> >>>
> >>> Fingerprint of the PGP key release artifacts are signed with:
> >>> 8FC8075E1FDC303276C676EE8001952629BCC75D
> >>>
> >>> My public key to verify signatures can be found in:
> >>> https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
> >>>
> >>> The vote will be open for at least 72 hours or until the necessary
> >>> number of votes are reached.
> >>>
> >>> Please vote accordingly:
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove (and the reason)
> >>>
> >>> Checklist for release:
> >>>
> >>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incuba
> >> tor+Release+Checklist
> >>> Steps to validate the release:
> >>> https://www.apache.org/info/verification.html
> >>>
> >>> * 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, LICENSE and NOTICE files are correct.
> >>> * All files have license headers if necessary.
> >>> * No unlicensed compiled archives bundled in source archive.
> >>> * The source tarball matches the git tag.
> >>> * Build from source is successful.
> >>>
> >>> Thanks,
> >>> Cheng Pan
> >>>
> >>
>

Reply via email to