docs: describe milestones in README

Also skip CI build on markdown-only changes

Author: lucas-koehler

.github/workflows/ci.yaml

@@ -1,6 +1,12 @@
 name: CI
 
-on: [push, pull_request]
+on:
+  push:
+    paths-ignore:
+      - '**.md'
+  pull_request:
+    paths-ignore:
+      - '**.md'
 
 jobs:
   ci:

README.md

@@ -26,6 +26,19 @@ In addition, EclipseSource also offers [professional support](https://jsonforms.
 
 See our [migration guide](https://github.com/eclipsesource/jsonforms/blob/master/MIGRATION.md) when updating JSON Forms.
 
+## Roadmap & Milestones
+
+The project roadmap can be found in [ROADMAP.md](./ROADMAP.md).
+
+Issues are sorted in one the following milestones that indicate when their implementation is planned.
+Independently of the assigned milestone, contributions are always accepted and appreciated.
+
+- A milestone for the next minor version. Issues planned to be implemented for the next release.
+- A milestone for the next major version. Issues planned to be implemented for the next major release.
+- A `.x` milestone. Issues which are concrete candidates for one of the next versions.
+- [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.
+
 ## Developers Documentation
 
 ### First time setup