mimaison commented on code in PR #589:
URL: https://github.com/apache/kafka-site/pull/589#discussion_r1506019540
##########
downloads.html:
##########
@@ -109,16 +109,16 @@ <h3 class="download-version">3.5.2<a href="#3.5.2"><i
class="fas fa-link " style
Released Dec 11, 2023
</li>
<li>
- <a
href="https://downloads.apache.org/kafka/3.5.2/RELEASE_NOTES.html";>Release
Notes</a>
+ <a
href="https://archive.apache.org/dist/kafka/3.5.2/RELEASE_NOTES.html";>Release
Notes</a>
Review Comment:
My understanding is that we use "best judgment" to select what to delete so
it may vary each time. Maybe deciding to keep all not EOL'ed releases in the
mirroring system would be a better process.
I'll undo the 3.5.2 changes and will keep this release in the mirroring
system for now.
> Is there something we can do in the release process to enforce this?
Some steps have to be performed by PMC members and once a release is
announced it's easy to move onto something else and not complete the post
release steps. If possible, yes we should try to automate as much as possible
but it's often tricky.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
