Change the release process to leverage the ASF infra hardware & network [LUCENE-6284]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
After all of the recent discussions, seems like it only makes sense to leverage the ASF infra hardware & network. We ran into multiple issues during the release of 5.0 due to known reliability issues with people.apache.org.
As the INFRA issue that was created ([INFRA-9170](https://issues.apache.org/jira/browse/INFRA-9170)) to get that fixed was closed as "won't fix" with a reason that they don't support hosting releases on people.apache.org.
Important NOTE: This is related but orthogonal to reducing artifacts size or retrying downloads.
---
Migrated from [LUCENE-6284](https://issues.apache.org/jira/browse/LUCENE-6284) by Anshum Gupta (@anshumg)
Contributor guide
Research direction
Start by reviewing the release of 5.0, the ASF INFRA-9170 issue, and the current use of people.apache.org. Done means defining and implementing a release process that uses ASF infrastructure hardware and network, separately from artifact-size reduction or download retries.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100