Should we write about we dropped Vim 7.3 support to Changes?
Open
Nobody has claimed this yet.
- Dominant language
- Vim Script
- Stars
- 587
- Forks
- 64
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 1
Description
#450 からずいぶん経ちましたが、今からでも Changes に書くべきだという意見がありました。
自分も書くべきだと思いますが、どうでしょうか。
Cc: @haya14busa
Contributor guide
No contributing guide indexed for this repository
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
Read issue #450 and the linked discussion to understand the decision to drop Vim 7.3 support, then inspect the repository's Changes document. Done means adding a clear note about the dropped support there, with wording agreed by the maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vim
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100