yes, you are right - this was changed in the main development branch but wasn’t backported to support/2.0 which is the branch that 2.0.x releases are built from. I have just added this commit to support/2.0 too and it will be released in the future in 2.0.9:
Unless you have specific requirements or unless you are directed to do otherwise by support, the software to use in production is the one that the documentation describes to install from packages, i.e. DEBs or RPMs : https://zato.io/docs/admin/guide/install/index.html In terms of which branch these packages are built from, this is support/2.0.
It’s also great to hear that you’d like to contribute to Zato! I’d like to guide you in the right direction but it would be very useful if you could describe a bit more what you are mostly interested in?
What particular branches of programming you find most rewarding? Frontend programming? Databases? API testing? Deployment automation? What libraries and frameworks do you like the most? What new would like you to see in Zato? What parts of Zato would you see extended to better cover your requirements at work?
Basically, I would like to suggest the parts of the project that best suit your needs and interests.