As far as I'm aware, this is enforced on us by the current plugin repository not supporting custom branches/hashes for plugin downloads? As soon thats fixed we are free to switch to doing dev on master for plugins, should we chose to.
-Michal On Wed, Sep 11, 2013 at 5:39 AM, Andrew Grieve <[email protected]> wrote: > Our 3.0 docs tell people to install plugins from master, so we really can't > be checking in directly to master. > > You can switch branches using: cordova-coho/coho foreach -r plugins "git > checkout dev" > > > On Tue, Sep 10, 2013 at 5:24 PM, Joe Bowser <[email protected]> wrote: > > > Hey > > > > So, I'm trying to catch up on all the changes that have been done, and > > I'm finding that EVERYTHING IS BROKEN! While a bunch of changes were > > done on master, they break what's on master in the plugins because we > > do plugin dev in the dev branch. Also, I don't see any documented way > > of switching to all the branches with coho that's documented, so I > > have no idea how we're supposed to do dev on this thing anymore. > > > > Can we please do the same thing with plugins that we do with the > > platforms? Plugins don't have to have the same version numbers as the > > platforms, but it would be good if master on the platforms matched up > > to what we would expect to see on the plugins. This dev branch crap is > > slowing things down and making things much harder. > > > > Joe > > >
