GehaFearless commented on PR #1681:
URL: 
https://github.com/apache/incubator-pegasus/pull/1681#issuecomment-1825113073

   Hi, huys. Thanks for U jobs!
   +1
   I checked:
   
   (yes) Do release files have the word incubating in their name?
   
   (yes) Are the digital signatures and hashes correct?
   
   (yes) Does a DISCLAIMER file exist?
   
   (yes) Do LICENSE and NOTICE files exist?
   
   (yes) Is the LICENSE and NOTICE text correct?
   
   (yes) Is the NOTICE year correct?
   
   (yes) Is there any 3rd party code contained inside the release? 
   
   (yes) Do the contents of the release match with what's tagged in 
version control?
   
   (no) Are there any unexpected binary files in the release?
   
   (yes) Can you compile from source? Are the instructions clear?
   
   
   
   
   Best regards, 
   
   Li GuoHao
   
   
   
   
   
   
   
   
   李国豪
   ***@***.***
   
   
   
    
   
   
   
   
   ------------------ 原始邮件 ------------------
   发件人:                                                                         
                                               "apache/incubator-pegasus"       
                                                                             
***@***.***>;
   发送时间: 2023年11月21日(星期二) 上午10:52
   ***@***.***>;
   ***@***.******@***.***>;
   主题: Re: [apache/incubator-pegasus] chore: bump the development version 
to 2.5.0 and release v2.5.0-RC1 (PR #1681)
   
   
   
   
   
    
   Merged #1681 into v2.5.
    
   —
   Reply to this email directly, view it on GitHub, or unsubscribe.
   You are receiving this because you commented.Message ID: ***@***.***>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to