@mjsax couple of questions 1 - "If we run the script to do the actual release, we have this information already" - Do you mean to say that we can get the current and previos release versions from git tags? like first fetch all the tags, sort in descending order and pick first and second indexed values are current and previos versions?
2 - "This allow us to call the new method from here, after we collected the information, but also at the end of the regular execution of the script and pass in the information directly. Thus, if a committer does a release, it's not required to call the script again but the email template will be generated directly" - The script 'release.py' if run, by default generates the email content for RC release for voting. At this point we are not ready for sending release completion announcement. So, what is point of generating the announcement email content at the end of the regular execution of the script 'release.py'? I mean, we need to send release announcement email only once voting is approved and we manually tag the release branch last commit with release version. [ Full content available at: https://github.com/apache/kafka/pull/5572 ] This message was relayed via gitbox.apache.org for [email protected]
