Our small studio has been using cocos2d-x for the past six months, we have made several modifications to cocos to reduce warning count and made several changes for the classes/framework to be const-correct. We recently updated to a new versions, and had to re-make many of those changes again for our code-base to work.
Const correctness is an important, and often overlooked, feature of C++ and other languages.
Compiling without warnings is another very good practice, and we would like to reduce the warning count in our builds so we can compile with warnings as errors, but going through the effort of fixing the warnings, just to update and have those changes reverted would be a waste of effort. How can we contribute these changes to the cocos builds so we can continue to update painlessly while keeping our code-base warning free and const-corrrect?