This is an automated email from the ASF dual-hosted git repository.
joewitt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nifi-site.git
The following commit(s) were added to refs/heads/main by this push:
new ff5e92c NIFI-9567
ff5e92c is described below
commit ff5e92c5243f6dbcda1a2fa05ddc34ab95dea24c
Author: Joe Witt <[email protected]>
AuthorDate: Wed Jan 19 11:20:42 2022 -0700
NIFI-9567
---
src/pages/markdown/release-guide.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/src/pages/markdown/release-guide.md
b/src/pages/markdown/release-guide.md
index d6b203b..8054c9e 100644
--- a/src/pages/markdown/release-guide.md
+++ b/src/pages/markdown/release-guide.md
@@ -202,10 +202,8 @@ problems that must be addressed before proceeding.
```
$ mvn install -Pcontrib-check,include-grpc
```
-1. Verify and update if necessary to ensure Docker version information points
to the next release version. For instance, if version being released is 1.9.0,
these values should be 1.9.0. This currently consists of three files:
- * [nifi-docker/dockerhub/Dockerfile, Line 25][dockerhub-version],
- * [nifi-docker/dockerhub/DockerImage.txt, Line 16][dockerimage-version] and
- * [nifi-docker/docker-compose/docker-compose.yml, Line
25][dockercompose-version].
+1. Verify and update if necessary to ensure Docker version information points
to the next release version. For instance, set correct release versions in
various Dockerfile files found in the codebase. There are approximately 5 to
update as of version 1.16.
+
### Step 3. Perform the release (RM)
1. Now its time to have maven prepare the release with this command.
