From the NAML documentation:
Versioning
Since users will be able to change the NAML code of their apps, Nabble must have a way to safely update its core (NAML and java classes) without breaking the user changes. The idea is to release new versions independently of the old versions and let users upgrade their custom code when they have time. Nabble will support a fixed number of versions and users will be forced to upgrade their code when they reach a version that is not supported anymore.
For now, serious users should contact the Nabble premium support in order to maintain their changes up-to-date and not worry about core upgrades. Can you guys explain what this means? It sounds like we should remove as much of my custom applications changes as possible?
HTTPS Please!