Gary Verhaegen 49b4a8dad8 tweak release process for more reliable labeling (#5823) ... Currently, there are quite a few releases that are lacking the Standard-Change label, even though they did publish artifacts. This makes our SOC2-compliance tracking a bit harder. For the past two months, I have manually added the label after-the-fact while preparing the monthly compliance report, but that doesn't seem like a great solution. This PR changes the release process to be more optimistic: assume the release is going to succeed by putting in the label immediately, and then (optionally) removing it if the release fails. Note that the label should only be removed in the rare case where the release was merged into master but somehow did not produce any artifact. This can only happen if the Linux build fails quite early, which as far as I know only happened once over the past two months when we had the release notes race condition. CHANGELOG_BEGIN CHANGELOG_END		2020-05-04 15:35:58 +02:00
..
src	Stop publishing to Bintray (#5422)	2020-04-03 16:22:00 +02:00
windows-installer	replace DAML Authors with DA in copyright headers (#5228)	2020-03-27 01:26:10 +01:00
artifacts.yaml	allow secure connection from JSON API to ledger (#5555)	2020-04-16 13:12:30 -04:00
BUILD.bazel	Build a zip containing all protobuf files (#5412)	2020-04-03 14:16:15 +02:00
install.bat	replace DAML Authors with DA in copyright headers (#5228)	2020-03-27 01:26:10 +01:00
install.sh	replace DAML Authors with DA in copyright headers (#5228)	2020-03-27 01:26:10 +01:00
RELEASE.md	tweak release process for more reliable labeling (#5823)	2020-05-04 15:35:58 +02:00
sdk-config.yaml.tmpl	Relabel "Experimental" to "Early Access" and reorganise pages (#5411)	2020-04-03 16:29:22 +02:00
util.bzl	Build a zip containing all protobuf files (#5412)	2020-04-03 14:16:15 +02:00