File tree Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Original file line number Diff line number Diff line change 1
1
## Roadmap
2
2
3
+ This is an overview of the roadmap.
4
+ The project is managed on Github's [ lib-bpmn-engine milestones] ( https://github.com/nitram509/lib-bpmn-engine/milestones ) page.
5
+
3
6
#### ✅ v0.1.0
4
7
5
- [ progress milestone v0.1.0] ( ///github.com/nitram509/lib-bpmn-engine/issues?q=is%3Aopen+is% 3Aissue+milestone%3Av0.1.0 )
8
+ [ progress milestone v0.1.0] ( ///github.com/nitram509/lib-bpmn-engine/issues?q=is%3Aissue+milestone%3Av0.1.0+is%3Aclosed )
6
9
7
10
For the first release I would like to have service tasks and events fully supported.
8
11
9
12
10
13
#### ✅ v0.2.0
11
14
12
- [ progress milestone v0.2.0] ( ///github.com/nitram509/lib-bpmn-engine/issues?q=is%3Aopen+is% 3Aissue+milestone%3Av0.2.0 )
15
+ [ progress milestone v0.2.0] ( ///github.com/nitram509/lib-bpmn-engine/issues?q=is%3Aissue+milestone%3Av0.2.0+is%3Aclosed )
13
16
14
17
With basic element support, I would like to add [ visualization/monitoring] ( ./advanced-zeebe.md ) capabilities.
15
18
If the idea of using Zeebe's exporter protocol is not too complex, that would be ideal.
@@ -19,7 +22,7 @@ Also, I would like to add [expression language support](./expression-syntax.md)
19
22
20
23
#### ⚙️ v0.3.0
21
24
22
- [ progress milestone v0.3.0] ( ///github.com/nitram509/lib-bpmn-engine/issues?q=is%3Aopen+is% 3Aissue+milestone%3Av0.3.0 )
25
+ [ progress milestone v0.3.0] ( ///github.com/nitram509/lib-bpmn-engine/issues?q=is%3Aissue+milestone%3Av0.3.0 )
23
26
24
27
One last but very important feature I aim for is the ability to load & store state.
25
28
Which means, that you as app developer would be able to persistent in-flight process instances
You can’t perform that action at this time.
0 commit comments