Hi, I noticed that we have not been deleting release candidates from subversion after they have been released and also we have not been deleting old releases. We are supposed to only maintain the latest release in subversion according to [1]. The release process documentation for most of the datafusion repos contains instructions on how to delete old releases.
Currently we have the following release candidates: apache-datafusion-44.0.0-rc1/ apache-datafusion-44.0.0-rc2/ apache-datafusion-45.0.0-rc1/ apache-datafusion-46.0.0-rc1/ apache-datafusion-46.0.0-rc2/ apache-datafusion-46.0.1-rc1/ apache-datafusion-comet-0.7.0-rc1/ apache-datafusion-python-44.0.0-rc1/ apache-datafusion-python-45.0.0-rc1/ apache-datafusion-python-45.0.0-rc2/ apache-datafusion-python-45.1.0-rc1/ apache-datafusion-python-45.2.0-rc2/ apache-datafusion-python-46.0.0-rc1/ apache-datafusion-sqlparser-rs-0.52.0-rc1/ apache-datafusion-sqlparser-rs-0.52.0-rc2/ apache-datafusion-sqlparser-rs-0.52.0-rc3/ apache-datafusion-sqlparser-rs-0.53.0-rc1/ apache-datafusion-sqlparser-rs-0.53.0-rc2/ apache-datafusion-sqlparser-rs-0.54.0-rc1/ apache-datafusion-sqlparser-rs-0.55.0-rc1/ And we have the following releases: datafusion-42.2.0/ datafusion-43.0.0/ datafusion-44.0.0/ datafusion-45.0.0/ datafusion-46.0.0/ datafusion-46.0.1/ datafusion-ballista-45.0.0/ datafusion-comet-0.7.0/ datafusion-python-43.1.0/ datafusion-python-44.0.0/ datafusion-python-45.2.0/ datafusion-python-46.0.0/ datafusion-sqlparser-rs-0.52.0/ datafusion-sqlparser-rs-0.53.0/ datafusion-sqlparser-rs-0.54.0/ datafusion-sqlparser-rs-0.55.0/ It would be great if we could start cleaning these up the next time we create a release of each project/subproject. Thanks, Andy. [1] https://www.apache.org/legal/release-policy.html#when-to-archive
