diff --git a/doc/05-Upgrading.md b/doc/05-Upgrading.md index 1c1d7c2dd..f7f8ec72a 100644 --- a/doc/05-Upgrading.md +++ b/doc/05-Upgrading.md @@ -42,15 +42,14 @@ use the tools provided by your database backend, like `mysqldump` or `pg_dump`. Restoring from a backup is trivial, and Director will always be able to apply pending database migrations to an imported old database snapshot. -Upgrading to 1.10.x +Upgrading to 1.11.x -------------------------------------------------- - Before upgrading, please upgrade the [incubator module](https://github.com/Icinga/icingaweb2-module-incubator) to (at least) v0.20.0. As always, you'll be prompted to apply pending Database Migrations. -Upgrading to 1.11.x +Upgrading to 1.10.x -------------------------------------------------- Please check module dependencies, we raised some of them. In case you're missing diff --git a/doc/82-Changelog.md b/doc/82-Changelog.md index 77a0cd2ab..6c0eebda9 100644 --- a/doc/82-Changelog.md +++ b/doc/82-Changelog.md @@ -11,11 +11,11 @@ Icinga Director v1.11 ships a nice new feature, which has been requested by many users: it is now possible to let Notification rules pick User and/or User Groups from Host and Service custom variables. -![82-1.11.0-05-notification_user-var.png](screenshot/director/82_changelog/v1.11.0/82-1.11.0-05-notification_user-var.png) +![Notification User Vars](screenshot/director/82_changelog/v1.11.0/82-1.11.0-05-notification_user-var.png) Behind the scenes, some Icinga DSL assures that Icinga behaves as expected: -![82-1.11.0-06-notification_user-var_rendered.png](screenshot/director/82_changelog/v1.11.0/82-1.11.0-06-notification_user-var_rendered.png) +![Notification User Vars rendered](screenshot/director/82_changelog/v1.11.0/82-1.11.0-06-notification_user-var_rendered.png) The IcingaDB module is now supported. This release also ships a fallback template for Icinga for Windows 1.11 (and Icinga 2.14). To improve security for those @@ -44,7 +44,7 @@ has been improved, Preview Diff shows more details, editing multiple single Services with the very same name has been fixed, and the interactive Startup log renderer now wraps log lines in a nice way: -![82-1_11_0-02-wrap-startup-log-lines.png](screenshot/director/82_changelog/v1.11.0/82-1.11.0-02-wrap_startup_log_lines.png) +![Wrap Startup Log lines](screenshot/director/82_changelog/v1.11.0/82-1.11.0-02-wrap_startup_log_lines.png) Performance has greatly been improved for those, who trigger a lot of single API requests, instead of relying on Import/Sync mechanism. Our template usage overview