Version annotations in capability matrix
Open
P3
project-management
website
wish
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Particularly once we get to the point of having a real, usable release, the capability matrix will be far more useful if we have annotations of which versions the capabilities refer to, both Beam versions and dependency versions (e.g. "requires Spark 2.0").
Imported from Jira [BEAM-166](https://issues.apache.org/jira/browse/BEAM-166). Original Jira may contain additional context.
Reported by: takidau.
Contributor guide
Research direction
Start by locating the capability matrix and review the original Jira issue BEAM-166 for its additional context. Determine how Beam and dependency versions such as Spark 2.0 should be represented, then verify that the matrix consistently identifies the versions associated with each capability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100