From af437e92d17ac3b1b4b0870f1dff4263fa6e252c Mon Sep 17 00:00:00 2001 From: Luiz Carvalho Date: Nov 28 2018 17:11:28 +0000 Subject: [PATCH 1/2] Add release notes for 0.9.9 Signed-off-by: Luiz Carvalho --- diff --git a/docs/release-notes.rst b/docs/release-notes.rst index db6b8e3..9596287 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -2,6 +2,29 @@ Release Notes ============= +Greenwave 0.9.9 +=============== + +Released 8 November 2018 + +* Undeprecate subject parameter for decision endpoint. This parameter is still + heavily used by Bodhi. It is done so because the subject parameter allows + clients to perform a single request to check the decision of various subjects. + +* Check RemoteRule configuration at start up time instead of during each + RemoteRule check. To allow RemoteRule functionality, the configuration must + contain the required dist-git and Koji URLs. As well as the RemoteRule policy. + +* Remove Bodhi dependency, i.e. asking for all builds from a Bodhi update. This + removes cyclic dependency (Bodhi depends on Greenwave) and simplifies the + code. Decision for bodhi_update no longer expands to include related + koji_build items from the Bodhi update. All builds have to be stated + explicitly in the "subject" field. Decision change message for bodhi_update is + no longer published if a test result changes for a koji_build in the Bodhi + update. As a side effect, the formerly deprecated "subject" field (replaced + with "subject_identifier" and "subject_type") has to be used to query for a + decision on multiple koji_builds. + Greenwave 0.9.8 =============== @@ -18,7 +41,7 @@ Released 17 October 2018 to define additional policies directly in the dist-git repo using a gating.yaml file. Checking the decision_context and others in gating.yaml files: use policies from remote gating.yaml files only if they match - `decision_context`, `product_version` and `subject_type` for current + `decision_context`, `product_version` and `subject_type` for current decision (as it's done for internal policies). * Adjust naming scheme for one prometheus metric according to the best From f1dbe244133ad82e761405556cb9588d92e301f4 Mon Sep 17 00:00:00 2001 From: Luiz Carvalho Date: Nov 28 2018 17:11:28 +0000 Subject: [PATCH 2/2] Add release notes for 0.9.10 Signed-off-by: Luiz Carvalho --- diff --git a/docs/release-notes.rst b/docs/release-notes.rst index 9596287..a106733 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -2,6 +2,22 @@ Release Notes ============= +Greenwave 0.9.10 +================ + +Released 29 November 2018 + +* Support for the new subject type redhat-module. + +* Subject type component-version is properly consumed in resultsdb-consumer. + +* Capitalize the first letter of the summary for a passing gating decision. + +* Support for SCM URLs without the `namespace`. When checking for RemoteRules in + artifact's originating SCM repository, it was assumed the repository was + always nested in a namespace. + + Greenwave 0.9.9 ===============