Last week we released Activiti Cloud Beta4 and moved straight away to the Beta5 planning. We are aiming to release Beta5 during the first week of January and currently we have 35 open issues: https://github.com/Activiti/Activiti/issues?q=is%3Aopen+is%3Aissue+milestone%3ABeta5
There has been also huge progress on automating our Docker Images and HELM charts generation for our example projects. This means that now you can find the examples being released and tested as part of our Java libraries lifecycle. There are a lot of improvements and refinements to cover, but the basics are already in place. You can find now our Docker Images being tagged with fixed versions at release time of the example repositories.
@daisuke-yoshimoto is working on improving autodeployment strategy issue. https://github.com/Activiti/Activiti/issues/2138
@constantin-ciobotaru Add more acceptance tests for the exporting applications.
worked on providing method for subprocess and changes for Audit EventConverters.
Worked on new examples pipeline. PR’s:
@igdianov Worked on the following PRs and Issues:
@miguelruizdev worked on testing Beta 4 release and conformance tests scenarios refactoring
@ryandawsonuk Updated ttc chart to use latest gateway version following upgrade to be boot 2.1. Ported a patch from PR to acceptance scenarios to fix step matching in security policy tests. Managed the release to maven central from bamboo. Updated quick starts and charts and added Beta4 entry to gitbook. Provided a way to extend keycloak realm at deploy time.
@erdemedeiros worked on Beta 4 release. Reviewed pending pull requests. Reviewed pending tasks for admin APIs.
@salaboy worked on testing Beta4 and updating dependencies after release. I fixed #2275 which demonstrated the power of our CI/CD approach for our community members, fixing a bug from report time to release time in less than 3hs.
Get in touch if you want to contribute: https://gitter.im/Activiti/Activiti7
We are looking forward to mentor people on the technologies that we are using to submit their first Pull Request