Re: Our Dev Flow Sucks
Also, coho has some nifty ways to filter the list of sub-projects (but not sub-modules) based on type (such as foreach plugin) On Wed, Sep 11, 2013 at 8:25 AM, Andrew Grieve wrote: > We're not using submodules :) > > > On Wed, Sep 11, 2013 at 11:21 AM, Bryan Bishop wrote: > > > On Wed, Sep 11, 2013 at 7:39 AM, Andrew Grieve > > wrote: > > > You can switch branches using: cordova-coho/coho foreach -r plugins > "git > > > checkout dev" > > > > Is there a reason this is using a coho command to run foreach ? For > > instance, there's git submodule --foreach I think. > > > > - Bryan > > http://heybryan.org/ > > 1 512 203 0507 > > >
Re: Our Dev Flow Sucks
We're not using submodules :) On Wed, Sep 11, 2013 at 11:21 AM, Bryan Bishop wrote: > On Wed, Sep 11, 2013 at 7:39 AM, Andrew Grieve > wrote: > > You can switch branches using: cordova-coho/coho foreach -r plugins "git > > checkout dev" > > Is there a reason this is using a coho command to run foreach ? For > instance, there's git submodule --foreach I think. > > - Bryan > http://heybryan.org/ > 1 512 203 0507 >
Re: Our Dev Flow Sucks
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 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 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 > > >
Re: Our Dev Flow Sucks
On Wed, Sep 11, 2013 at 7:39 AM, Andrew Grieve wrote: > You can switch branches using: cordova-coho/coho foreach -r plugins "git > checkout dev" Is there a reason this is using a coho command to run foreach ? For instance, there's git submodule --foreach I think. - Bryan http://heybryan.org/ 1 512 203 0507
Re: Our Dev Flow Sucks
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 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 >
Our Dev Flow Sucks
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
