When we started the ERP projects our main goal was to publish the alpha360 data models; the WX projects where just "limited core" projects to help developers better understand the data models.
Things have changed a lot since the early days of the projects and - especially with v2 - they are now more complete; more developers are using them to develop their own solutions.
So what is the best way to "follow up" with NEWER versions and "include" new features of the projects in YOUR solutions?
Starting with version 2 releases, all projects, have now a reference version; this is always the first, non beta release [with the exception of the Retail project] - release 2.07 is the reference version for all projects.
All our additions and changes are done with reference to version 2.07 and the details are included inside the projects. So a simple search, say for 2.08, is sufficient to find all changes and additions we have done in v2.08.
There are also some great features in the WX IDE; you can Search for last changes, compare projects etc.
Just note that you should also use some kind of notation in YOUR projects to "label" YOUR changes or additions.
A good practice would also be to create YOUR own windows or reports, instead of doing extended changes to ours and of course label them accordingly.
We can also include YOUR code/changes directly in newer versions, if we think they are of GENERAL INTEREST; but note that they will be available to all licensees.
The above does not affect in-house developers with a consultancy contract - their changes and additions are always kept synchronized by our developers.