Describe milestones in README #2352
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for jsonforms-examples ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
sdirix
reviewed
Jul 5, 2024
README.md
Outdated
Comment on lines
36
to
40
| - [3.4](https://github.com/eclipsesource/jsonforms/milestone/57): Issues which we plan to implement for the upcoming 3.4 release. | ||
| - [4.0](https://github.com/eclipsesource/jsonforms/milestone/55): Issue which we plan to implement for the next major release 4.0. This is the next planned version after the 3.4. release. | ||
| - [4.x](https://github.com/eclipsesource/jsonforms/milestone/58): Issues which are concrete candidates for one of the next versions after the 4.0 release. | ||
| - [next](https://github.com/eclipsesource/jsonforms/milestone/37): Issues which we would like to tackle soonish in one of the upcoming versions. However, they are not yet planned for a specific version. | ||
| - [Backlog](https://github.com/eclipsesource/jsonforms/milestone/2): Issues which are interesting in some form but we don't plan to do ourselves in the foreseeable future. Still these might become part of JSON Forms via a community contribution or by prioritization of a paying customer. |
There was a problem hiding this comment.
I would describe this process generically, so we don't need to update the Readme for every milestone change.
lucas-koehler
force-pushed
the
lk/describe-milestones
branch
from
e5d1a16
to
acb98ee
Compare
sdirix
approved these changes
Aug 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I closed the 3.x milestone as we plan 4.0. after 3.4. All open issues from 3.x were moved to 4.x