Improve release building automation

[Chris Sharp]

The Evergreen release building team has a few hurdles that could probably be solved by better coordination and automation:

1) The release notes building process is done manually and is a prerequisite to building the release. Release building is often delayed because no one on the build team is sure of who is responsible for release notes building and the current status. Release notes builders have confirmed that the manual process is slow and cumbersome.

2) The release building process is poorly documented. The most up-to-date documentation I am aware of is on the wiki (https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8) and has remained mostly static since the 2.X days.

3) Several developers have scripts to automate parts of the build process, but they are disparate and probably out of date (speaking for my own such script).

Creating a well-documented, comprehensive, automated build process will increase the efficiency of building major and minor releases and allow for better planning and more community volunteer involvement opportunities.

[Chris Sharp (chrissharp123)]

We have a running scratchpad document here: https://docs.google.com/document/d/1WKyOSasnREy8-jAy00O1XrZyGbpd9efWPFFDSn0UZPI/edit

[Jane Sandberg (sandbergja)]

FWIW, I put together a Perl script that pulls some data from launchpad (about the bug fix) and git commits (about who did the work) and assembles a draft of some point release notes. It can be found here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/sandbergja/point_release_notes_script

General usage instructions:

1) Check out a release branch (example: git checkout rel_3_8)
2) Determine the last commit that was included in the previous release
3) run perl build/tools/point_release_notes.pl NEW_VERSION_NUMBER PREVIOUS_VERSION_NUMBER LAST_COMMIT_OF_PREVIOUS_VERSION (for example, perl build/tools/point_release_notes.pl 3.8.7 3.8.6 aec34d12
4) This will print a draft of your release notes to your console. Copy that into the relevant docs/RELEASE_NOTES file (for example, docs/RELEASE_NOTES_3_8.adoc)

It is not great by any means, but I've used it the past few times that I've wanted to do release notes, and it saved me some time.