spring-projects / spring-projects/spring-data-commons
Productize release train machinery?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 838
- Forks
- 730
- PR merge metrics
- No merged PRs in 30d
Description
NB: I'm not sure that this is the correct project to file this issue in, but it's a start. Feel free to close with direction on which Spring project to file this issue in.
IMHO, Spring Data has one of the most mature release processes in the industry, especially with the notion of release trains. This can probably be said of many Spring projects now.
I'm wondering if the Spring team would consider productizing the release train machinery and make it available as an open source project. I feel like many companies/dev teams could benefit from the rigor & best practices that your release train process employs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes productizing Spring Data's release train machinery but names no files, tests, or entry points. First clarify whether spring-data-commons is the right project and define the desired scope with the Spring team. Done would require a maintainer-approved direction for whether and where this work should proceed.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100