I'm trying to finish up the work on CB-7291 (The external launch whitelist
for Android) and I'm running into some conceptual issues with the upgrade
scripts that we have currently.
The problems come from the fact that some upgrades should only be done
once, and that upgrading is done at a platform
Personally, I think we could just document the steps to manually update the
config.xml's.
We have no concept at all of CLI project upgrades. If we change the
default hooks/ format, or remove merges/ by default, you have to re-create
the project to see those changes. I think this is similar. If
Documentation is definitely a way out of this. I'd like to avoid the
developer hassle that we introduced with File, when upgrading meant that
previously working behaviour suddenly stopped working, so I'm trying to
explore other alternatives first.
On Fri, Aug 22, 2014 at 2:24 PM, Michal Mocny wr
