Last week we worked quite hard to close some critical issues to be able to release Beta3, which is now work in progress. You can find the issues that we manage to close here: https://github.com/Activiti/Activiti/milestone/15?closed=1. Most of the work that we are planning for Beta4 is about Conformance Tests, Acceptance Tests and automation to make sure that our release cycles can include more value after each iteration. We are currently looking into automate our examples layer to maintain a stable environment where we can promote new versions of the libraries as explained here: https://salaboy.com/2018/11/05/activiti-cloud-ci-cd-approach-for-java-libraries-and-beyond/https://salaboy.com/2018/11/05/activiti-cloud-ci-cd-approach-for-java-libraries-and-beyond/
@igdianovworked on decorating events with BusinessKey for correlation
@constantin-ciobotaruworked on modeling side to adapt the ModelService to json based model types
@miguelruizdevworked on the first iteration of the acceptance tests main refactoring
@ryandawsonukAligned query and runtime bundle task variablesby copying process variables into task as a precursor to providing variable mappings. Fixed bugaffecting runtime task lists for users with no groups.
@erdemedeirosfix issue related to task updated event (https://github.com/Activiti/Activiti/issues/2129). Started thinking about the evolutions of admin APIs.
@salaboyworking on the first iteration of the conformance testing framework to check valid Core and Cloud scenarios. You can find the work in progress in this branch: https://github.com/activiti/activiti/tree/2128-salaboy-conformance-testsand issue https://github.com/Activiti/Activiti/issues/2128https://github.com/Activiti/Activiti/issues/2128
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 
