[
https://issues.apache.org/jira/browse/KAFKA-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873909#comment-17873909
]
Mickael Maison commented on KAFKA-17328:
----------------------------------------
We should be able to keep the overall release process and switch to use
dist.apache.org/dev/kafka to host RCs.
If I understand correctly, the main difference is that we could access
home.apache.org over sftp, while dist.apache.org is only accessible over svn.
We are already using dist.apache.org (but /release/kafka) to store releases so
we can reuse these steps. This would be a good time to automate these steps too.
We might also want to add a cleanup step once a release is complete so we
delete RCs from dist.apache.org/dev/kafka.
> Update Release.py script to point to dist.apache.org/dev
> --------------------------------------------------------
>
> Key: KAFKA-17328
> URL: https://issues.apache.org/jira/browse/KAFKA-17328
> Project: Kafka
> Issue Type: Task
> Components: release
> Reporter: Josep Prat
> Priority: Major
> Labels: release
>
> Infra communicated the decommission of the home.apache.org box. This box was
> used by the Release manager to store the RC candidates up for vote. The box
> will be decommissioned in 4 weeks (around September 10th 2024)
> The release.py script is written to push the artifacts in the RM's home box.
> We need to update this process and use the dist.apache.org/dev space.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
