Describe milestones in README by lucas-koehler · Pull Request #2352 · eclipsesource/jsonforms
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
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. |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would describe this process generically, so we don't need to update the Readme for every milestone change.
sdirix
deleted the
lk/describe-milestones
branch
This file contains hidden or 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