Added fixed issues to the 1.7.187 release changelog (#6740)

changelog.md

@@ -1,14 +1,36 @@
-## Changes to 1.7.xxx
+## Changes to 1.7.187
+
+### Java 9+ 
+
+In jdk9 `javax.annotation` is not present by default, and marathon can't start due to jersey requires it. This fix adds this dependency to our build enabling Marathon to start on Java 9+.
 
 ### Apps names restrictions (breaking change)
 
 From now on, apps which uses ids which ends with "restart", "tasks", "versions" won't be valid anymore. Such apps already had broken behavior (for example it wasn't possible to use a `GET /v2/apps` endpoint with them), so we made that constraint more explicit. Existing apps with such names will continue working, however all operations on them (except deletion) will result in an error. Please take care of renaming them before upgrading Marathon.
 
-
 ### Default for "kill_retry_timeout" was increased to 30 seconds
 
 Sending frequent kill requests to an agent can in certain cases lead to overloading the Docker daemon (if the tasks are docker containers run by the Docker containerizer). Thirty seconds seems to be a more sensible default here. 
 
+### Fixed issues:
+
+- [MARATHON-8498](https://jira.mesosphere.com/browse/MARATHON-8498) - Fixed a secrets validator error which previously did not allow the users to submit a change to a secret environment variable without also submitting the corresponding secrets section.
+- [MARATHON-8493](https://jira.mesosphere.com/browse/MARATHON-8493) - Fixed a rare precision issue when computing resources needed to start a pod. Additionally, we now count in executor GPU resources when computing the resource consumption. 
+- [MARATHON-8453](https://jira.mesosphere.com/browse/MARATHON-8453) - Fixed a bug where overdue tasks (those that take too much time to start) would be killed without taking `--kill_retry_timeout` parameter into consideration. In some cases that would lead to too many kill requests being sent to Mesos. Three additional metrics were introduced to give users more insights into task killing statistics:
+    - `marathon.instances.overdue.gauge` - the number of overdue instances. Overdue
+      instances are those that have been either launched or staged but hasn't
+      become running within the `task_launch_timeout` or `task_launch_confirmation_timeout`
+      respectively.
+    - `marathon.instances.doomed.gauge` - the current number of instances for which
+      Marathon has sent a kill request but hasn't received a confirmation from
+      Mesos yet.
+    - `instances.doomed.kill-attempts.gauge` - the total number of kill attempts that
+      Marathon has sent for all currently existing doomed instances.
+- [MARATHON-8413](https://jira.mesosphere.com/browse/MARATHON-8413) - Fixed broken versioning of Apps and Pods in Java9+ due to the fact that JDK9 started capturing nanoseconds when `Instant.now()` was called.
+- [MARATHON-8466](https://jira.mesosphere.com/browse/MARATHON-8466) - From now on, apps which uses ids which ends with "restart", "tasks", "versions" won't be valid anymore. Such apps already had broken behavior, so we made that constraint more explicit. Existing apps with such names will continue working, however all operations on them (except deletion) will result in an error.
+
+## Changes to 1.7.174
+
 ### Marathon framework ID generation is now very conservative
 
 Previously, Marathon would automatically request a new framework ID from Mesos if the old one was marked as torn down in Mesos, or if the framework ID record was removed from Zookeeper. This has led to more trouble than it has helped. The new behavior is: