prepare-release should put changesToHtml and KEYS output in dist/ [LUCENE-3954]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Currently changes2html output is in build/docs/changes
But really, this just means RM must manually deal with it separately from dist/
I think 'prepare-release' should ensure dist/ houses everything that goes into the RC,
Additionally, KEYS files for both lucene/solr which should be fetched from
http://people.apache.org/keys/group/lucene.asc automatically.
Sorry, i know there are python scripts etc in dev-tools as well as ant logic
to do some of this, but it would be much easier for 'prepare-release' to
actually make the full release, and some people don't want to give their
ssh password to any script like that.
---
Migrated from [LUCENE-3954](https://issues.apache.org/jira/browse/LUCENE-3954) by Robert Muir (@rmuir), updated May 09 2016
Contributor guide
Research direction
Start by locating the prepare-release entry point and tracing how changes2html currently writes to build/docs/changes and how dist/ is assembled. Read the related scripts in dev-tools and the Ant release logic, then verify that the release contents include the generated changesToHtml output and the Lucene and Solr KEYS files fetched from the stated URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- build-system, release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100