Release notes 1.4.0 (#180)

* moving to WebLogic Remote Console 2.4.1

* adding release notes for 1.4.0

* edits

* adding Verrazzano install bug fix to the release notes

* adding another bug fixed

* updating release notes

Author: robertpatrick

documentation/staging/1.4/content/release/_index.md

@@ -5,34 +5,39 @@ weight = 7
 pre = "<b> </b>"
 +++
 
-### Changes in Release 1.3.0
+### Changes in Release 1.4.0
 - [Major New Features](#major-new-features)
 - [Other Changes](#other-changes)
 - [Bugs Fixes](#bug-fixes)
 - [Known Issues](#known-issues)
 
 
 #### Major New Features
-- Support for creating and deploying the Verrazzano component for the WebLogic domain, and an application that references it.  
+- #173: Added support for WebLogic Kubernetes Operator 4.0.  While it is now the default, versions 3.3+ are still supported.  
 
 #### Other Changes
-- Updated the [WebLogic Remote Console](https://github.com/oracle/weblogic-remote-console) integration to support version 2.4.0.
-- Added support for specifying node selectors when installing the WebLogic Kubernetes Operator and deploying the WebLogic
-  domain, either directly or as a Verrazzano component.
-- Added support for the user specifying the Helm timeout value when helm is used (i.e., Installing/updating WebLogic
-  Kubernetes Operator and installing the Ingress Controller).
-- Added tooltips across all icon buttons to describe what they do.
-- Added an anti-affinity specification to the generated WebLogic domain resource, as recommended by the WebLogic Kubernetes Operator docs.
+- #175: Added Zoom In, Zoom Out, and Actual Size menu options to the Window menu.
+- #178: Integrated the `Prepare Model` action with the changes in WebLogic Deploy Tooling 2.4.0.
+- #179: Updated the [WebLogic Remote Console](https://github.com/oracle/weblogic-remote-console) integration to support version 2.4.1 (2.4.0 also supported).
 
 #### Bug Fixes
-- Fixed an issue introduced by newer WDT versions that was forcing the domain cluster size to only allow replicas to be set to 0 (WKTUI-365).
-- #164: Fixed the link in the Introduction dialog to open in the user's browser instead of inside the app.
-- #167: Improved the validation logic and error messages around having an empty model.
-- #170: Worked around an issue that was limiting the ability to select text from the Code View scripts (WKTUI-375).
+- #171: Improved workaround for the issue limiting the ability to select text from the Code View scripts (WKTUI-375).
+- #172: Resolved issue when using Domain-in-Image that was causing the domain to not be created.
+- #174: Resolved an issue where the `Install Ingress Controller` action was always passing the image pull secret--even when the user indicated not to use one. 
+- #176: Resolved an issue where the `Update Ingress Routes` action was always passing the `SSL pass-through` argument--even when the user did not request it.
+- #182: Resolved Verrazzano 1.4.0+ installation issue caused by a change in the published operator file name. 
+- #186: Resolved Verrazzano-related issue where Ingress Trait rules were not including the hosts or destination-related fields.
+- #187: Resolved an issue where the operator domain variable override config map was not being created properly.
+- #187: Resolved an issue with the `apiVersion` of the Verrazzano component- and application-related being incorrect.
 
 #### Known Issues
 - On Linux, the open and save dialogs open behind the main application window.  This is due to
   [Electron bug 32857](https://github.com/electron/electron/issues/32857).
 - When deploying a Verrazzano application, the `Check Application Status` button only checks the status of the project's
   Verrazzano component containing the WebLogic domain specification.
-- Due to the workaround for WKTUI-375, users are not able to tab to the script area of the Code View pages.
+- WKTUI does not currently show the Verrazzano URL needed to access the application.  The URL will always be of
+  the form `https://<gateway-hostname>/<app-path>`, where the `gateway-hostname` is the name created by Verrazzano
+  in the `Gateway` object.  To get the name of the generated gateway object, run `kubectl get gateway -n <namespace> --template
+  '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}'`.  Next, run `kubectl get gateway <gateway-name> -n <namespace> -o yaml`
+  and review the `hosts` entry of the `.spec.servers` section to find the DNS name that corresponds to the
+  `gateway-hostname` to use in the URL.

documentation/staging/1.4/content/release/release-1.3.0.md

@@ -0,0 +1,38 @@
++++
+title = "Release 1.3.0"
+date = 2022-01-30T12:48:00-05:00
+weight = 7
+pre = "<b> </b>"
++++
+
+### Changes in Release 1.3.0
+- [Major New Features](#major-new-features)
+- [Other Changes](#other-changes)
+- [Bugs Fixes](#bug-fixes)
+- [Known Issues](#known-issues)
+
+
+#### Major New Features
+- Support for creating and deploying the Verrazzano component for the WebLogic domain, and an application that references it.  
+
+#### Other Changes
+- Updated the [WebLogic Remote Console](https://github.com/oracle/weblogic-remote-console) integration to support version 2.4.0.
+- Added support for specifying node selectors when installing the WebLogic Kubernetes Operator and deploying the WebLogic
+  domain, either directly or as a Verrazzano component.
+- Added support for the user specifying the Helm timeout value when helm is used (i.e., Installing/updating WebLogic
+  Kubernetes Operator and installing the Ingress Controller).
+- Added tooltips across all icon buttons to describe what they do.
+- Added an anti-affinity specification to the generated WebLogic domain resource, as recommended by the WebLogic Kubernetes Operator docs.
+
+#### Bug Fixes
+- Fixed an issue introduced by newer WDT versions that was forcing the domain cluster size to only allow replicas to be set to 0 (WKTUI-365).
+- #164: Fixed the link in the Introduction dialog to open in the user's browser instead of inside the app.
+- #167: Improved the validation logic and error messages around having an empty model.
+- #170: Worked around an issue that was limiting the ability to select text from the Code View scripts (WKTUI-375).
+
+#### Known Issues
+- On Linux, the open and save dialogs open behind the main application window.  This is due to
+  [Electron bug 32857](https://github.com/electron/electron/issues/32857).
+- When deploying a Verrazzano application, the `Check Application Status` button only checks the status of the project's
+  Verrazzano component containing the WebLogic domain specification.
+- Due to the workaround for WKTUI-375, users are not able to tab to the script area of the Code View pages.