In the past I've used #3. When checking out code to test, I try to get all the assets from the same branch / time period. But I may be skewed in that approach, since our product that embeds Cordova has a snapshot of the platforms and plugins, and doesn't get updates from the online repos.
Does what you are saying infer that the rename of the plugins is a breaking change? And needs to have some verbage in the Upgrading guides? On Oct 1, 2013, at 11:14 AM, David Kemp <drk...@chromium.org> wrote: > Summary: Due to the renaming of plugins, there is no longer a sensible way > to test 3.0.x > > Detail: > The process to test 3.0.x is to get platforms, mobile-spec, etc from 3.0.x > and plugins from master. With the change on plugin names (remove core) the > 3.0.x mobile-spec still refers to the names with core , but the master > branch of the plugins no longer have that name. > > Possible resolutions: > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed in 3.1.x > 2) cherrypick the change to mobilespec dependencies back to 3.0.x > 3) find some other way to get the older plugins available to test. > > Thoughts? > > David Kemp
