Date for 2.0-rc2

Author: rjeberhard

README.md

@@ -22,7 +22,7 @@ The fastest way to experience the operator is to follow the [Quick Start guide](
 
 ```diff
 + The current release of the operator is 2.0-rc2, a release candidate for our 2.0 release.
-+ This release candidate was published on Jan. 17, 2019.
++ This release candidate was published on Jan. 16, 2019.
 + We expect to publish the final 2.0 release later in January, 2019.
 + We expect that there will be some minor changes to documentation and samples in the final 2.0 release.
 + However, this release candidate is suitable for testing and early adopters.

site/recent-changes.md

@@ -4,7 +4,7 @@ This document tracks recent changes to the operator, especially ones that introd
 
 | Date | Version | Introduces backward incompatibilities | Change |
 | --- | --- | --- | --- |
-| January 17, 2019 | v2.0-rc2 | yes | Schema updates are completed, and various bugs fixed.
+| January 16, 2019 | v2.0-rc2 | yes | Schema updates are completed, and various bugs fixed.
 | December 20, 2018 | v2.0-rc1 | yes | Operator is now installed via Helm charts, replacing the earlier scripts.  The operator now supports the domain home on persistent volume or in Docker image use cases, which required a redesign of the domain schema.  You can override the domain configuration using configuration override templates.  Now load balancers and Ingresses can be independently configured.  You can direct WebLogic logs to a persistent volume or to the pod's log.  Added lifecycle support for servers and significantly enhanced configurability for generated pods.  The final v2.0 release will be the initial release where the operator team intends to provide backward compatibility as part of future releases.
 | March 20, 2018 | v1.1 | yes | Several files and input parameters have been renamed.  This affects how operators and domains are created.  It also changes generated Kubernetes artifacts, therefore customers must recreate their operators and domains.
 | April 4, 2018 | v1.0 | yes | Many Kubernetes artifact names and labels have changed. Also, the names of generated YAML files for creating a domain's PV and PVC have changed.  Because of these changes, customers must recreate their operators and domains.