Define roadmap for 4.0.0
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C++
- Stars
- 50.6k
- Forks
- 7.5k
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 58
Description
As discussed in https://github.com/nlohmann/json/pull/3444#discussion_r857072525, we currently have no single place to collect all things deemed to wait until the next breaking change.
The goal for this issue is to have a document in the repository to sketch what will come with 4.0.0.
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
Start by reading the discussion linked from issue #3453, especially the conversation on pull request #3444. Identify the changes intended to wait for the next breaking release and determine where the repository's roadmap document should live. Done means a repository document clearly sketches the planned 4.0.0 scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100