Add EOL process doc
Open
type/feature
- Dominant language
- Go
- Stars
- 52.3k
- Forks
- 10.5k
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 44
Description
### What would you like to be added?
Related to `release.md`, we should also have a process doc for how versions are EOL'd. This is a little more than we want to put into release.md itself, I think, but that file would link to this one.
### Why is this needed?
Currently we don't have a doc for this at all.
Contributor guide
Research direction
Start by reading release.md to understand the existing release documentation and where a link to the new process belongs. Document how etcd versions are EOL'd, using the project's established release process as guidance, and consider the work done when the standalone document is complete and release.md links to it.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100