[
https://issues.apache.org/jira/browse/KUDU-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666664#comment-16666664
]
Grant Henke commented on KUDU-1404:
-----------------------------------
[~s...@apache.org] We just released 1.8.0 adding another version to the
release directory. I suspect that is what is triggering this request.
Our release notes mention removing old releases in step #12 here:
[https://github.com/apache/kudu/blob/master/RELEASING.adoc#release]
Our release directory contains 6 releases that are currently active:
{noformat}
1.3.1, 1.4.0, 1.5.0, 1.6.0, 1.7.1, 1.8.0
{noformat}
The documentation states that we should keep 1 copy of each active branch. We
branch for each minor version. There are definitely people using 1.3 and 1.4
releases, but it is debatable if we would backport and release in the 1.3 and
1.4 releases, so perhaps we could remove those soon.
That said is there something that triggered this clean up request? Is there a
maximum number of "active development branches" we should be staying under? Is
6 too many?
> Please delete old releases from mirroring system
> ------------------------------------------------
>
> Key: KUDU-1404
> URL: https://issues.apache.org/jira/browse/KUDU-1404
> Project: Kudu
> Issue Type: Bug
> Environment: http://www.apache.org/dist/incubator/kudu/
> Reporter: Sebb
> Assignee: Jean-Daniel Cryans
> Priority: Major
> Fix For: n/a
>
>
> To reduce the load on the ASF mirrors, projects are required to delete old
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> Note: you can still reference superseded versions from the download page, but
> the links should be adjusted to point to the archive server.
> [1] http://www.apache.org/dev/release.html#when-to-archive
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
