elastic / elastic/elastic-package
Simplifying package release process proposal
- Dominant language
- Go
- Stars
- 72
- Forks
- 141
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 55
Description
Hello team, as Package Registry V2 is here we are in the position to enhance our package release process even more!
I started working on a [document](https://docs.google.com/document/d/1K6SH_m0MAg2PFw1ACbJlc4-h62VgiZ5-thY6cc8tW-k/edit?usp=sharing) to sketch how we could improve the package release process by building on top of what Package Registry V2 provides.
/cc @ruflin @elastic/ecosystem
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Google document, which sketches improvements to the package release process using Package Registry V2. Confirm the intended scope, affected release entry points, and acceptance criteria with the maintainers; the issue does not identify files, tests, or a defined completion state.
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
- 20/100