Last week was all about planning for the next iteration plus trying to solve some critical issues that we found while doing Beta2 release. Beta3 will come quite fast, we hope accelerate the release cycle for the Beta phase to make sure that we fix well known issues and we provide consumable artifacts for community users. If you find issues with Beta2please feel free to report, comment and vote issues here: https://github.com/activiti/activiti/issues
@balsaroriworked on exposing form key to process definition and task #2082
@constantin-ciobotaruworked to adapt the APS modeling to new activiti Beta2 modeling zip structure
@miguelruizdevworked on the refactoring and the increase of coverage of the acceptance tests.
@ryandawsonukUpdated the gitbook with details of migration from beta1 to beta2 and updated charts README to clarify how to enable modeling. Ran through the slackbot demo together with @miguelruizdevand @erdemedeiroto define, raise and address a related set of issues on task visibility in query.
@erdemedeirosworked with @ryandawsonukto identify the cause of main issues in query service (https://github.com/Activiti/Activiti/issues/2092, https://github.com/Activiti/Activiti/issues/2093, https://github.com/Activiti/Activiti/issues/2103). Fixed those issues.
@salaboyworked on new scenarios conformance document, organizing the GitHub issues under Beta3 milestone, planning and creating a new stable set 7.0.55 for activiti-cloud-dependencies.
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 
