Hey I just noticed that there's been a ton of new commits on the 4.0.x branch, many of which change some public-facing APIs of Cordova. Landing this many patches into Cordova without bringing these up on the list isn't OK, since many of these changes will break any hope of an upgrade path for our users.
Can we please make sure that heavy refactors happen on independent branches and are discussed on the list before they land in a release branch? I know that 4.0.x is a long way off, but I was planning to demo some of our work at OSCON, and the recent changes broke the demo. I now have to fork off the branch before this refactor was done, which sucks because we can't get any new people who want to contribute on-boarded easily. I really don't want to revert everything, because that would suck, but being patchbombed sucks as well, and doesn't help build consensus with other people on the project. Also, I'm not sure we can revert this git repo back, because Apache git is weird and doesn't allow force. I know that availability is limited, but a heads up would be good, since I have no idea what is going on with a lot of these commits, since some are the opposite of what we agreed to earlier. Interested in hearing thoughts about the changes, and how we can avoid this in the future. Joe
