+1

Looks like there are various optimizations.

Thanks,
Ethan Feng

[email protected] <[email protected]> 于2026年4月18日周六 23:31写道:
>
> +1&nbsp;approve,Thanks to Nicholas Jiang for releasing Apache Celeborn 
> 0.6.3-rc1.
>
>
> Regards,
> Zhaohui Xu
>
>
> ------------------ Original ------------------
> From: Nicholas <[email protected]&gt;
> Date: Thu,Apr 16,2026 3:55 PM
> To: dev <[email protected]&gt;
> Subject: Re: [VOTE] Release Apache Celeborn 0.6.3-rc1
>
>
>
> Hi&nbsp;Celeborn&nbsp;community,
>
>
> This&nbsp;is&nbsp;a&nbsp;call&nbsp;for&nbsp;a&nbsp;vote&nbsp;to&nbsp;release&nbsp;Apache&nbsp;Celeborn
> 0.6.3-rc1
>
>
> The&nbsp;git&nbsp;tag&nbsp;to&nbsp;be&nbsp;voted&nbsp;upon:
> https://github.com/apache/celeborn/releases/tag/v0.6.3-rc1
>
>
> The&nbsp;git&nbsp;commit&nbsp;hash:
> f583b73d292afdfeed865e20610838121c9db9cf&nbsp;source&nbsp;and&nbsp;binary&nbsp;artifacts&nbsp;can&nbsp;be&nbsp;found&nbsp;at:
> https://dist.apache.org/repos/dist/dev/celeborn/v0.6.3-rc1
>
>
> The&nbsp;staging&nbsp;repo:
> https://repository.apache.org/content/repositories/orgapacheceleborn-1134
>
>
> Fingerprint&nbsp;of&nbsp;the&nbsp;PGP&nbsp;key&nbsp;release&nbsp;artifacts&nbsp;are&nbsp;signed&nbsp;with:&nbsp;92B13217E2AD1470D58882EF7B41580856A83A36
>
>
> My&nbsp;public&nbsp;key&nbsp;to&nbsp;verify&nbsp;signatures&nbsp;can&nbsp;be&nbsp;found&nbsp;in:
> https://dist.apache.org/repos/dist/release/celeborn/KEYS
>
>
> The&nbsp;vote&nbsp;will&nbsp;be&nbsp;open&nbsp;for&nbsp;at&nbsp;least&nbsp;72&nbsp;hours&nbsp;or&nbsp;until&nbsp;the&nbsp;necessary&nbsp;number&nbsp;of&nbsp;votes&nbsp;are&nbsp;reached.
>
>
> Please&nbsp;vote&nbsp;accordingly:
>
>
> [&nbsp;]&nbsp;+1&nbsp;approve
> [&nbsp;]&nbsp;+0&nbsp;no&nbsp;opinion
> [&nbsp;]&nbsp;-1&nbsp;disapprove&nbsp;(and&nbsp;the&nbsp;reason)
>
>
> Steps&nbsp;to&nbsp;validate&nbsp;the&nbsp;release:
> https://www.apache.org/info/verification.html
>
>
> *&nbsp;Download&nbsp;links,&nbsp;checksums&nbsp;and&nbsp;PGP&nbsp;signatures&nbsp;are&nbsp;valid.
> *&nbsp;Source&nbsp;code&nbsp;distributions&nbsp;have&nbsp;correct&nbsp;names&nbsp;matching&nbsp;the&nbsp;current&nbsp;release.
> *&nbsp;LICENSE&nbsp;and&nbsp;NOTICE&nbsp;files&nbsp;are&nbsp;correct.
> *&nbsp;All&nbsp;files&nbsp;have&nbsp;license&nbsp;headers&nbsp;if&nbsp;necessary.
> *&nbsp;No&nbsp;unlicensed&nbsp;compiled&nbsp;archives&nbsp;bundled&nbsp;in&nbsp;source&nbsp;archive.
> *&nbsp;The&nbsp;source&nbsp;tarball&nbsp;matches&nbsp;the&nbsp;git&nbsp;tag.
> *&nbsp;Build&nbsp;from&nbsp;source&nbsp;is&nbsp;successful.
>
>
> Regards,
> Nicholas&nbsp;Jiang

Reply via email to