Kaileshwar16 opened a new issue, #888:
URL: https://github.com/apache/wayang/issues/888

   I was going through wayang's release process and noticed that there are 
quite a few manual steps involved.
   
   I was thinking whether we could automate some of these steps to reduce 
manual effort and avoid possible errors during releases.
   
   A few things we could consider:
   
   #### 1. Pre-release checks
   - Check whether the Git working tree is clean.
   - Verify that version numbers are consistent across Maven modules.
   - Check whether the required release notes and documentation are present.
   - Verify that the required build and tests have passed.
   
   #### 2. Release candidate validation
   - Check whether the expected release artifacts are generated.
   - Verify checksums and GPG signatures.
   - Check whether the source archive contains the required `LICENSE` and 
`NOTICE` files.
   
   #### 3. Release preparation
   - Generate a simple release checklist.
   - Provide a summary of passed and failed checks, possibly through GitHub 
Actions later.
   
   
   I donot think we should automate too much at once, as it might make the 
release process harder to debug and maintain.
   
   maybe we could start with a small release readiness script that handles the 
basic checks and gradually extend it only where needed. we should also try to 
reuse existing CI checks rather than introduce duplicate workflows.
   
   
   I came across rustup from the rust ecosystem and thought something along 
these lines might be useful for Wayang as well.
   
   would like to know what others think about this and whether we already have 
some of these checks in place.


-- 
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]

Reply via email to