[GitHub] [avro] RyanSkraba commented on pull request #1570: AVRO-3423: Add build.sh step to encapsulate all the steps needed during release

[GitBox <gi...@apache.org>]

RyanSkraba commented on pull request #1570:
URL: https://github.com/apache/avro/pull/1570#issuecomment-1054528562


   I really like one advantage of this -- I have tons of notes (in addition to the wiki) for releasing binary artifacts and doing the equivalent of `verify-release`.  I've always intended to clean my notes up and contribute them back, and it would be really neat to do that in the build scripts themselves.
   
   Unfortunately, I'm kind of skittish about delegating these steps to a script and generalizing them to all languages...  I'd find it hard to "trust" doing a `./build.sh release` from the root and have all of the binary artifacts deployed -- especially if there were failures midway or _something unexpected happens_  (it always does).
   
   Note that the Wiki process isn't immune to that either (check out the Python SDK release 1.9.2.1 as an example of fixing a bad deploy!)
   
   I don't have any good ideas for that other than prompting `(y/n/skip)` at each command!  Any ideas?
   
   


-- 
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: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org