Operator version 3.0.2 #1912
Operator version 3.0.2 #1912
Conversation
…ator Helm chart and related doc change
…tor .out, and document log rotation for WLS .out and .log.
…Exceeded (which happens when intro job times out due to DeadlineExceeded).
|
What is the process of adding bug fixes? It doesn't look as though you are cherry-picking commits merged into develop, as you've been squashing the PRs to single commits, and here you seem to be using the original commits on the branch. How will this affect merging future work from develop into master? |
|
I cherry-picked the commits from the original PR's. |
|
After we merge to master, I'll merge master back into develop to make sure that there are no conflicts (there shouldn't be). |
|
What is the advantage of doing that vs. cherry-picking the squashed commits? |
| | --- | --- | --- | --- | | ||
| | September 15, 2020 | v3.0.2 | no | This release contains several fixes, including improvements to log rotation and a fix that avoids unnecessarily updating the domain status. | |
There was a problem hiding this comment.
Can we list the fixes that went into 3.0.2 for user reference?
| @@ -4,7 +4,7 @@ date: 2019-03-15T11:25:28-04:00 | |||
| draft: false | |||
| --- | |||
|
|
|||
| ### Recent changes | |||
| ### Releases | |||
|
|
|||
| | Date | Version | Introduces backward incompatibilities? | Changes | | |||
There was a problem hiding this comment.
Changes -> Change (I let this go before but it was a mistake. It should be singular, Change, just like all the other headings are singular, Date, Version, Issue, and Description. The question mark after Introduces backward incompatibilities? is ok.) I looked at the Change log in the Hugo UI and it all looks fine, definitely good to go.
We are planning to release another set of bug fixes.
The following PR's were selected based on customer impact and severity:
Additionally, the following PR's were required because one or more of the PR's in the above list depended on these changes:
Based on a review request, additionally added