Hi Folks, First, big +1 to @msbeard for building an amazing release pipeline. Intuitive guide and great release scripts. This was a snap.
Second, I haven’t officially staged any release candidates on repository.apache.org <http://repository.apache.org/>. I won’t until @msbeard or MENTORS change our dist repo names to reflect “flagon”. I ran “dry-run” versions of @msbeard’s release scripts and copied over the artifacts and sigs into the staging area at https://dist.apache.org/repos/dist/dev/incubator/senssoft/ <https://dist.apache.org/repos/dist/dev/incubator/senssoft/>. I also updated Keys. A quick look at .asc files shows sigs are properly authenticating. Third, I have modified release scripts for new dist URLs, git repos and naming conventions to reflect flagon name changes. Until such time as the dist urls are updated to /flagon, the release scripts will break if not run in “dry-run” mode. [ACTION] Please Mentors and @msbeard, take a quick look at what’s on dist/dev staging area and give a sense for whether it looks right. This is probably a good idea given that this is my first time playing release-manager. If so, and when dist names are updated, I’ll officially stage the release candidates for review by PMC and we’ll get this official re-release done. Thanks All! Josh
