diff --git a/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version.mdwn b/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version.mdwn
index 888e185668..3f1f3bce41 100644
--- a/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version.mdwn
+++ b/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version.mdwn
@@ -41,3 +41,5 @@ $> git tag | grep 202108
 ```
 
 so it seems odd
+
+> [[notabug|done]] --[[Joey]]
diff --git a/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version/comment_1_337c17e686723aee193e898fd7ee3558._comment b/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version/comment_1_337c17e686723aee193e898fd7ee3558._comment
new file mode 100644
index 0000000000..d03bd9b94e
--- /dev/null
+++ b/doc/bugs/downloads.kitenet.net_do_not_correspond_in_version/comment_1_337c17e686723aee193e898fd7ee3558._comment
@@ -0,0 +1,21 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2021-08-09T16:11:54Z"
+ content="""
+6e67ea5d7 is 2 commits away from the tag for 8.20210803. 
+The two commits are whitespace changes and the commit that increased the
+version number.
+
+I can either push the release to git and bless the builds current at the
+same time, or wait some amount of time after the release tag for the builds
+to catch up. That could be some arbitrary amount of time, because builds
+fail for various reasons outside my control, or are slow.
+
+It would also need a separate build process than the autobuilds of master,
+to build against release tags. Which adds even more ways for things to go
+wrong or be delayed.
+
+Therefore, I have chosen this compromise. It is not new, and if you
+consider it a bug, well, you can build against the release tag if you wish.
+"""]]