in reply to (OT) Sponsoring open source

In programming structuring you could add the subroutines as empty-ready routines in the public version and put the code in the "bleeding edge development version"; you will be able to get way ahead towards both your customer and the public API.

Your clients will get the bleeding edge versions; while the public version will already be feature-ready for the bleeding edge patches. This way you can steam the people ready for using these development versions.