Re: Cordova Committer Hangout notes
Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com
Re: A few comments on Working With 3.0
It sounds like you're installed npm packages with dependencies (coho, cordova-js) and not running npm install. That command will install all their dependencies locally. In particular that's what's wrong with grunt-cli vs. grunt: the intended flow is that you install grunt-cli globally, and that gives you a grunt command. That command is a thin wrapper the looks up your directory structure until it finds a node_modules/grunt, and then runs that locally installed grunt version. Braden On Wed, Aug 14, 2013 at 6:50 PM, James Jong wjamesj...@gmail.com wrote: Becky, I would update your cordova-ios project. There was a recent change to remove it (CB-4281). -James Jong On Aug 14, 2013, at 5:33 PM, Becky Gibson gibson.be...@gmail.com wrote: OK, I think the linker problem is because CDVEcho.m is included twice. I see it in plugins dir under org.apache.cordova.test.echo/src/ios/ and in platforms/ios/cordovalib/classes/. I'm guessing this has something to do with the dependencies for mobilespec? thanks, -becky On Wed, Aug 14, 2013 at 5:05 PM, Becky Gibson gibson.be...@gmail.com wrote: I found a few bugs in iOS media capture and media that I would like to fix. I need to get set up for 3.0 so I followed the instructions here: http://wiki.apache.org/cordova/WorkingWithThree. Since I didn't have any 3.0 clones I started by cloning. Here are a few issues that I ran into that did not seem to be documented: - In order for the coho clone command to work I needed to install optimist, shelljs and request. I tried to install optimist globally but that didn't work so I ended up installing all of these locally in my cordova-coho directory to get things working. - I had to blindly cut and paste the coho clone from the WorkingWithThree wiki page since I couldn't find any documentation for the clone command. - I edited .cordova/config.json as indicated in the instructions but then running the cordova platform add command kept giving me a syntax error: unexpected string. I went back to the default config.json and the platform add command worked correctly. - Since I was starting from scratch I had to also clone cordova-js - I followed the instructions for the cordova-js readme and installed grunt via: sudo npm install -g grunt-cli When I tried to run grunt to build cordova-js I got the message that it should be installed locally: Fatal error: Unable to find local grunt. Based on the original instructions I installed grunt-cli locally - that didn't work so I installed grunt locally. - I could build the platform js files but got the following error: Running _test task starting node-based tests Warning: can't run tests in node: run grunt btest instead, or install jsdom via: npm install Use --force to continue. Since I didn't care about the tests (at this point I didn't worry about the error - however I'm still not sure what I should be installing). I opened the created mobilespec project in xcode but the build failed when linking. I did make the mistake of opening it in xcode 5 (beta 5) before trying it in 4.6 so my project settings may have been messed up by xcode 5. I'll tackle that tomorrow but I wanted to get the installation information documented before I forgot. -becky
Re: A few comments on Working With 3.0
Regarding cordova-ios, I cloned a cordova-ios into a new directory via the coho clone script in the wiki. I assumed that would get me the latest but I'll update and see what happens. I'm not sure what installing the packages with dependencies means? I ran npm install -g. I'm no node expert, what should I have done? It would at least be good to document the coho dependencies in the readme. Regarding grunt vs grunt-cli - I did run sudo npm install -g grunt-cli and it got installed but still wasn't accessible from cordova-js? thanks, -becky On Thu, Aug 15, 2013 at 9:33 AM, Braden Shepherdson bra...@chromium.orgwrote: It sounds like you're installed npm packages with dependencies (coho, cordova-js) and not running npm install. That command will install all their dependencies locally. In particular that's what's wrong with grunt-cli vs. grunt: the intended flow is that you install grunt-cli globally, and that gives you a grunt command. That command is a thin wrapper the looks up your directory structure until it finds a node_modules/grunt, and then runs that locally installed grunt version. Braden On Wed, Aug 14, 2013 at 6:50 PM, James Jong wjamesj...@gmail.com wrote: Becky, I would update your cordova-ios project. There was a recent change to remove it (CB-4281). -James Jong On Aug 14, 2013, at 5:33 PM, Becky Gibson gibson.be...@gmail.com wrote: OK, I think the linker problem is because CDVEcho.m is included twice. I see it in plugins dir under org.apache.cordova.test.echo/src/ios/ and in platforms/ios/cordovalib/classes/. I'm guessing this has something to do with the dependencies for mobilespec? thanks, -becky On Wed, Aug 14, 2013 at 5:05 PM, Becky Gibson gibson.be...@gmail.com wrote: I found a few bugs in iOS media capture and media that I would like to fix. I need to get set up for 3.0 so I followed the instructions here: http://wiki.apache.org/cordova/WorkingWithThree. Since I didn't have any 3.0 clones I started by cloning. Here are a few issues that I ran into that did not seem to be documented: - In order for the coho clone command to work I needed to install optimist, shelljs and request. I tried to install optimist globally but that didn't work so I ended up installing all of these locally in my cordova-coho directory to get things working. - I had to blindly cut and paste the coho clone from the WorkingWithThree wiki page since I couldn't find any documentation for the clone command. - I edited .cordova/config.json as indicated in the instructions but then running the cordova platform add command kept giving me a syntax error: unexpected string. I went back to the default config.json and the platform add command worked correctly. - Since I was starting from scratch I had to also clone cordova-js - I followed the instructions for the cordova-js readme and installed grunt via: sudo npm install -g grunt-cli When I tried to run grunt to build cordova-js I got the message that it should be installed locally: Fatal error: Unable to find local grunt. Based on the original instructions I installed grunt-cli locally - that didn't work so I installed grunt locally. - I could build the platform js files but got the following error: Running _test task starting node-based tests Warning: can't run tests in node: run grunt btest instead, or install jsdom via: npm install Use --force to continue. Since I didn't care about the tests (at this point I didn't worry about the error - however I'm still not sure what I should be installing). I opened the created mobilespec project in xcode but the build failed when linking. I did make the mistake of opening it in xcode 5 (beta 5) before trying it in 4.6 so my project settings may have been messed up by xcode 5. I'll tackle that tomorrow but I wanted to get the installation information documented before I forgot. -becky
Re: A few comments on Working With 3.0
yeah, sounds like mainly it's that you missed typing npm install within cordova-js and within cordova-coho (and within cordova-cli if you want to use a local version of that). For iOS (and android), the WorkingWithThree steps exist in a script within cordova-mobile-spec (createmobilespec.sh). For coho - use coho --help for documentation. On Thu, Aug 15, 2013 at 9:33 AM, Braden Shepherdson bra...@chromium.orgwrote: It sounds like you're installed npm packages with dependencies (coho, cordova-js) and not running npm install. That command will install all their dependencies locally. In particular that's what's wrong with grunt-cli vs. grunt: the intended flow is that you install grunt-cli globally, and that gives you a grunt command. That command is a thin wrapper the looks up your directory structure until it finds a node_modules/grunt, and then runs that locally installed grunt version. Braden On Wed, Aug 14, 2013 at 6:50 PM, James Jong wjamesj...@gmail.com wrote: Becky, I would update your cordova-ios project. There was a recent change to remove it (CB-4281). -James Jong On Aug 14, 2013, at 5:33 PM, Becky Gibson gibson.be...@gmail.com wrote: OK, I think the linker problem is because CDVEcho.m is included twice. I see it in plugins dir under org.apache.cordova.test.echo/src/ios/ and in platforms/ios/cordovalib/classes/. I'm guessing this has something to do with the dependencies for mobilespec? thanks, -becky On Wed, Aug 14, 2013 at 5:05 PM, Becky Gibson gibson.be...@gmail.com wrote: I found a few bugs in iOS media capture and media that I would like to fix. I need to get set up for 3.0 so I followed the instructions here: http://wiki.apache.org/cordova/WorkingWithThree. Since I didn't have any 3.0 clones I started by cloning. Here are a few issues that I ran into that did not seem to be documented: - In order for the coho clone command to work I needed to install optimist, shelljs and request. I tried to install optimist globally but that didn't work so I ended up installing all of these locally in my cordova-coho directory to get things working. - I had to blindly cut and paste the coho clone from the WorkingWithThree wiki page since I couldn't find any documentation for the clone command. - I edited .cordova/config.json as indicated in the instructions but then running the cordova platform add command kept giving me a syntax error: unexpected string. I went back to the default config.json and the platform add command worked correctly. - Since I was starting from scratch I had to also clone cordova-js - I followed the instructions for the cordova-js readme and installed grunt via: sudo npm install -g grunt-cli When I tried to run grunt to build cordova-js I got the message that it should be installed locally: Fatal error: Unable to find local grunt. Based on the original instructions I installed grunt-cli locally - that didn't work so I installed grunt locally. - I could build the platform js files but got the following error: Running _test task starting node-based tests Warning: can't run tests in node: run grunt btest instead, or install jsdom via: npm install Use --force to continue. Since I didn't care about the tests (at this point I didn't worry about the error - however I'm still not sure what I should be installing). I opened the created mobilespec project in xcode but the build failed when linking. I did make the mistake of opening it in xcode 5 (beta 5) before trying it in 4.6 so my project settings may have been messed up by xcode 5. I'll tackle that tomorrow but I wanted to get the installation information documented before I forgot. -becky
Re: A few comments on Working With 3.0
https://npmjs.org/doc/faq.html is a good resource for understanding node's local vs global dependencies. Agree coho's README needs updating. It's completely out of date! On Thu, Aug 15, 2013 at 11:20 AM, Andrew Grieve agri...@chromium.orgwrote: yeah, sounds like mainly it's that you missed typing npm install within cordova-js and within cordova-coho (and within cordova-cli if you want to use a local version of that). For iOS (and android), the WorkingWithThree steps exist in a script within cordova-mobile-spec (createmobilespec.sh). For coho - use coho --help for documentation. On Thu, Aug 15, 2013 at 9:33 AM, Braden Shepherdson bra...@chromium.orgwrote: It sounds like you're installed npm packages with dependencies (coho, cordova-js) and not running npm install. That command will install all their dependencies locally. In particular that's what's wrong with grunt-cli vs. grunt: the intended flow is that you install grunt-cli globally, and that gives you a grunt command. That command is a thin wrapper the looks up your directory structure until it finds a node_modules/grunt, and then runs that locally installed grunt version. Braden On Wed, Aug 14, 2013 at 6:50 PM, James Jong wjamesj...@gmail.com wrote: Becky, I would update your cordova-ios project. There was a recent change to remove it (CB-4281). -James Jong On Aug 14, 2013, at 5:33 PM, Becky Gibson gibson.be...@gmail.com wrote: OK, I think the linker problem is because CDVEcho.m is included twice. I see it in plugins dir under org.apache.cordova.test.echo/src/ios/ and in platforms/ios/cordovalib/classes/. I'm guessing this has something to do with the dependencies for mobilespec? thanks, -becky On Wed, Aug 14, 2013 at 5:05 PM, Becky Gibson gibson.be...@gmail.com wrote: I found a few bugs in iOS media capture and media that I would like to fix. I need to get set up for 3.0 so I followed the instructions here: http://wiki.apache.org/cordova/WorkingWithThree. Since I didn't have any 3.0 clones I started by cloning. Here are a few issues that I ran into that did not seem to be documented: - In order for the coho clone command to work I needed to install optimist, shelljs and request. I tried to install optimist globally but that didn't work so I ended up installing all of these locally in my cordova-coho directory to get things working. - I had to blindly cut and paste the coho clone from the WorkingWithThree wiki page since I couldn't find any documentation for the clone command. - I edited .cordova/config.json as indicated in the instructions but then running the cordova platform add command kept giving me a syntax error: unexpected string. I went back to the default config.json and the platform add command worked correctly. - Since I was starting from scratch I had to also clone cordova-js - I followed the instructions for the cordova-js readme and installed grunt via: sudo npm install -g grunt-cli When I tried to run grunt to build cordova-js I got the message that it should be installed locally: Fatal error: Unable to find local grunt. Based on the original instructions I installed grunt-cli locally - that didn't work so I installed grunt locally. - I could build the platform js files but got the following error: Running _test task starting node-based tests Warning: can't run tests in node: run grunt btest instead, or install jsdom via: npm install Use --force to continue. Since I didn't care about the tests (at this point I didn't worry about the error - however I'm still not sure what I should be installing). I opened the created mobilespec project in xcode but the build failed when linking. I did make the mistake of opening it in xcode 5 (beta 5) before trying it in 4.6 so my project settings may have been messed up by xcode 5. I'll tackle that tomorrow but I wanted to get the installation information documented before I forgot. -becky
Re: Cordova Committer Hangout notes
Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Re: Cordova Committer Hangout notes
I think I remember hearing from a very smart person: Shipping in a predictable manner drives adoption, and confidence, in an open source project. Confidence in the health of a project attracts contributors. Committers are our soul, and releases our heartbeat... On Thu, Aug 15, 2013 at 11:28 AM, Carlos Santana csantan...@gmail.comwrote: Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Re: Cordova Committer Hangout notes
I think it was earlier discussed that we would skip August and have a September 3.1 (or whatever we call it now) release. -Michal On Thu, Aug 15, 2013 at 11:28 AM, Carlos Santana csantan...@gmail.comwrote: Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Re: Cordova Committer Hangout notes
Absolutely, but the regular cadence historically still didn't include every month. The schedule set 1 year in advance has 10 releases, skipping august after a major release and december since everyone is on vacation. If there is reason to release now, I'm sure arguments will be heard! On Thu, Aug 15, 2013 at 11:34 AM, Carlos Santana csantan...@gmail.comwrote: I think I remember hearing from a very smart person: Shipping in a predictable manner drives adoption, and confidence, in an open source project. Confidence in the health of a project attracts contributors. Committers are our soul, and releases our heartbeat... On Thu, Aug 15, 2013 at 11:28 AM, Carlos Santana csantan...@gmail.com wrote: Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Re: Cordova Committer Hangout notes
Smart! (Thx Carlos. =) [1] We traditionally have let Aug and December go as that Aug gave us more hardening the new shiny and nobody really works in Dec anyhow. ;) [1] http://www.youtube.com/watch?v=tcGQpjCztgA On Thu, Aug 15, 2013 at 8:34 AM, Carlos Santana csantan...@gmail.comwrote: I think I remember hearing from a very smart person: Shipping in a predictable manner drives adoption, and confidence, in an open source project. Confidence in the health of a project attracts contributors. Committers are our soul, and releases our heartbeat... On Thu, Aug 15, 2013 at 11:28 AM, Carlos Santana csantan...@gmail.com wrote: Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Re: Cordova Committer Hangout notes
Good to know Brian. Then Sep. release might align better with new iOS7 and give more time to make the new shinny more robust On Thu, Aug 15, 2013 at 12:02 PM, Brian LeRoux b...@brian.io wrote: Smart! (Thx Carlos. =) [1] We traditionally have let Aug and December go as that Aug gave us more hardening the new shiny and nobody really works in Dec anyhow. ;) [1] http://www.youtube.com/watch?v=tcGQpjCztgA On Thu, Aug 15, 2013 at 8:34 AM, Carlos Santana csantan...@gmail.com wrote: I think I remember hearing from a very smart person: Shipping in a predictable manner drives adoption, and confidence, in an open source project. Confidence in the health of a project attracts contributors. Committers are our soul, and releases our heartbeat... On Thu, Aug 15, 2013 at 11:28 AM, Carlos Santana csantan...@gmail.com wrote: Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Re: A few comments on Working With 3.0
FYI I'm guessing that the cordova-mobile-spec\dependencies-plugin\plugin.xml file is what is causing the problems with the xcode project since it still lists org.apache.test.echo as a dependency. I guess my point in the first post was to point out the difficulties in following the WorkingWithThree instructions in hopes of helping other folks who might want to contribute. I DID run npm install moduleName from the directory that had the dependency to get a local copy. My question was really whether or not we intended for the modules to be installed locally rather than globally. Looking at .gitignore I guess the intention is for local install since node_modules is listed. On Thu, Aug 15, 2013 at 11:24 AM, Andrew Grieve agri...@chromium.orgwrote: https://npmjs.org/doc/faq.html is a good resource for understanding node's local vs global dependencies. Agree coho's README needs updating. It's completely out of date! On Thu, Aug 15, 2013 at 11:20 AM, Andrew Grieve agri...@chromium.org wrote: yeah, sounds like mainly it's that you missed typing npm install within cordova-js and within cordova-coho (and within cordova-cli if you want to use a local version of that). For iOS (and android), the WorkingWithThree steps exist in a script within cordova-mobile-spec (createmobilespec.sh). For coho - use coho --help for documentation. On Thu, Aug 15, 2013 at 9:33 AM, Braden Shepherdson bra...@chromium.org wrote: It sounds like you're installed npm packages with dependencies (coho, cordova-js) and not running npm install. That command will install all their dependencies locally. In particular that's what's wrong with grunt-cli vs. grunt: the intended flow is that you install grunt-cli globally, and that gives you a grunt command. That command is a thin wrapper the looks up your directory structure until it finds a node_modules/grunt, and then runs that locally installed grunt version. Braden On Wed, Aug 14, 2013 at 6:50 PM, James Jong wjamesj...@gmail.com wrote: Becky, I would update your cordova-ios project. There was a recent change to remove it (CB-4281). -James Jong On Aug 14, 2013, at 5:33 PM, Becky Gibson gibson.be...@gmail.com wrote: OK, I think the linker problem is because CDVEcho.m is included twice. I see it in plugins dir under org.apache.cordova.test.echo/src/ios/ and in platforms/ios/cordovalib/classes/. I'm guessing this has something to do with the dependencies for mobilespec? thanks, -becky On Wed, Aug 14, 2013 at 5:05 PM, Becky Gibson gibson.be...@gmail.com wrote: I found a few bugs in iOS media capture and media that I would like to fix. I need to get set up for 3.0 so I followed the instructions here: http://wiki.apache.org/cordova/WorkingWithThree. Since I didn't have any 3.0 clones I started by cloning. Here are a few issues that I ran into that did not seem to be documented: - In order for the coho clone command to work I needed to install optimist, shelljs and request. I tried to install optimist globally but that didn't work so I ended up installing all of these locally in my cordova-coho directory to get things working. - I had to blindly cut and paste the coho clone from the WorkingWithThree wiki page since I couldn't find any documentation for the clone command. - I edited .cordova/config.json as indicated in the instructions but then running the cordova platform add command kept giving me a syntax error: unexpected string. I went back to the default config.json and the platform add command worked correctly. - Since I was starting from scratch I had to also clone cordova-js - I followed the instructions for the cordova-js readme and installed grunt via: sudo npm install -g grunt-cli When I tried to run grunt to build cordova-js I got the message that it should be installed locally: Fatal error: Unable to find local grunt. Based on the original instructions I installed grunt-cli locally - that didn't work so I installed grunt locally. - I could build the platform js files but got the following error: Running _test task starting node-based tests Warning: can't run tests in node: run grunt btest instead, or install jsdom via: npm install Use --force to continue. Since I didn't care about the tests (at this point I didn't worry about the error - however I'm still not sure what I should be installing). I opened the created mobilespec project in xcode but the build failed when linking. I did make the mistake of opening it in xcode 5 (beta 5) before trying it in 4.6 so my project settings may have been messed up by xcode 5. I'll tackle that tomorrow but I wanted to get the
Re: Cordova Committer Hangout notes
Let's try and start the 3.1 release testing first week of sept. It'll be the first release of this new world, so will probably take longer than usual. It'd be good to have it out before PGD EU (on the 24th) On Thu, Aug 15, 2013 at 1:15 PM, Carlos Santana csantan...@gmail.comwrote: Good to know Brian. Then Sep. release might align better with new iOS7 and give more time to make the new shinny more robust On Thu, Aug 15, 2013 at 12:02 PM, Brian LeRoux b...@brian.io wrote: Smart! (Thx Carlos. =) [1] We traditionally have let Aug and December go as that Aug gave us more hardening the new shiny and nobody really works in Dec anyhow. ;) [1] http://www.youtube.com/watch?v=tcGQpjCztgA On Thu, Aug 15, 2013 at 8:34 AM, Carlos Santana csantan...@gmail.com wrote: I think I remember hearing from a very smart person: Shipping in a predictable manner drives adoption, and confidence, in an open source project. Confidence in the health of a project attracts contributors. Committers are our soul, and releases our heartbeat... On Thu, Aug 15, 2013 at 11:28 AM, Carlos Santana csantan...@gmail.com wrote: Forgot to mention during the meeting that there was an Elephant in the hangout. Are we going to have a Cordova Release for this month (August 2013)? --Carlos On Thu, Aug 15, 2013 at 10:50 AM, James Jong wjamesj...@gmail.com wrote: I think u mean The Fancy Pants Podcast? -James Jong On Aug 15, 2013, at 7:23 AM, Carlos Santana csantan...@gmail.com wrote: Thanks for the notes. Great hagout last night it was great meeting everyone. Now that we have the Cordova Blog maybe we should think about The Cordova Podcast :-) --Carlos On Wednesday, August 14, 2013, Brian LeRoux wrote: http://goo.gl/8xL4m8 (LMK if you want access.) -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com -- Carlos Santana csantan...@gmail.com
Merge plugin dev branchs into master
I want to try and flush out the process for merging the dev branches for the core plugins into master and get it onto the wiki. Currently the dev branches have some readme changes, namespace changes and package changes for android. I don't believe any of these changes should be breaking changes. Process 1. Create issue on jira for running mobile spec tests on all platforms using dev branch of plugins 2. Test on all platforms 3. Merge in change into master 4. Publish to plugins.cordova.io? Do we really need to test the plugins on all the platforms for changes that won't affect them at all?
Re: Storing Version Numbers
Wiki page updated (and renamed):
https://wiki.apache.org/cordova/StoringRepoVersionsDesign
On Wed, Aug 14, 2013 at 5:20 PM, Ian Clelland iclell...@google.com wrote:
On Wed, Aug 14, 2013 at 4:09 PM, Jesse purplecabb...@gmail.com wrote:
I like the transparency of simply having a VERSION file at the root of
any
cordova project. Can't we just remove the extra steps with the git hash
checking?
It used to be the case that Android would use the git hash of cordova-js as
it's version -- that's no longer the case.
I haven't checked whether any of the other platforms are still doing that,
but if so, they should stop.
We can still keep the hash in cordova.js; it helps us tell exactly which
version has been embedded in a particular project. We just shouldn't
pretend that it reliably indicates the platform version as well.
Ian
@purplecabbage
risingj.com
On Wed, Aug 14, 2013 at 12:44 PM, Filip Maj f...@adobe.com wrote:
Looks good to me!
On 8/14/13 11:49 AM, Andrew Grieve agri...@chromium.org wrote:
Ian's put together a wiki page on how to store version numbers in our
repos:
https://wiki.apache.org/cordova/PlatformVersionScripts
I'd like to add info to it for non-platform repos as well, but want to
draw
everyone's attention to it on the ML so that we can have easier
comments
about it:
= All Repositories =
'''Proposal'''
VERSION files go away. None of the below schemes use them, so they
should
be added only when building Apache release .zips.
= Cordova platforms =
Cordova platforms should have a simple, reliable method to report
their
version number, for use by automated tools such as CLI and plugman.
The current method for doing this (supported by Android; support
coming
for
other platforms) is to have a script in the platform package, under
`bin/templates/cordova/version`, which can be called to report the
version
number.
Previously, this file would, on some platforms, go through some rather
complicated process to infer the correct version number (such as
checking
the git hash of the included cordova.js file). It will be simpler and
easier to maintain to have this file simply echo a string constant.
The version number should correspond closely to the git branch. When a
release branch is made, both the branch and the master branch should
be
updated. The master branch should *always* have a version number
ending
in
-dev, which indicates the version currently being developed. A fresh
release branch should change the version to an -rc1 version, and
then
change to the unqualified version number when it is released.
(This constant version number can be updated manually, but *should*
eventually be updated via coho as release branches are made.)
This should give a rough idea how the version number should advance:
{{{
3.3.0-dev
3.2.0-dev|
| |
--A---B---C---D (master)
\
\--E---F---G---H (3.2.x)
| | |
3.2.0-rc1| 3.2.1-rc1
3.2.0
}}}
* A: This is on the master branch, after 3.1.x has been branched, as
3.2
is being developed.
* B: This is the branch point for 3.2.x
* C: The first commit after 3.2.x is branched should identify the
master
branch as 3.3 is being developed on master now.
* E: The first commit on the 3.2.x branch should identify the branch
as
3.2.0-rc1
* G: At some point, 3.2.0 is released, and should be identified as
such
* H: After 3.2.0 is released, any further development can be called
3.2.1-rc1
Current support:
||'''Platform'''||'''Support'''||
||Android || {*} ||
||BB10 || {o} ||
||iOS || {o} ||
||OSX || {o} ||
||QT|| {o} ||
||Tizen || {o} ||
||WebOS || {o} ||
||Win || {o} ||
||WP7 || {o} ||
||WP8 || {o} ||
||www || {o} ||
= Cordova JS =
The version of the JS is stamped at the top of the built .js file by
grunt.
Currently, the version is derived using `git describe` and so is based
off
of the closest git tag in the history. This works well for releases,
but
isn't great for dev builds since there are no tags made on master.
'''Proposal:'''
1. Follow platform versioning scheme and store it in a constant
within
Gruntfile.js.
1. When in built in the context of a git repo, and not at a tagged
commit,
append the git hash.
1. When not in a git repo or at a tagged commit, don't try and
append a
hash.
= Core Plugins =
Current state is that we have master dev branches. This is because
plugman pulls from master by default, so it must remain
Re: Merge plugin dev branchs into master
Great! I agree it's time someone take a stab at this! On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill stevengil...@gmail.com wrote: I want to try and flush out the process for merging the dev branches for the core plugins into master and get it onto the wiki. Currently the dev branches have some readme changes, namespace changes and package changes for android. I don't believe any of these changes should be breaking changes. Process 1. Create issue on jira for running mobile spec tests on all platforms using dev branch of plugins 2. Test on all platforms 3. Merge in change into master 4. Publish to plugins.cordova.io? Do we really need to test the plugins on all the platforms for changes that won't affect them at all? I think no. And we should only test plugins that have changes to them (in this case all of them). Should add in bumping of the version number. I think one thing to add to the process is to create mobilespec with the existing versions of plugins, then `cordova plugin rm` them all, then `cordova plugin add` the new ones using a URL that points to the dev branch. aka, test out the upgrade process.
Re: Merge plugin dev branchs into master
Thanks for the feedback Andrew! Sounds good to me. I am going to go through these steps today. On Thu, Aug 15, 2013 at 12:07 PM, Andrew Grieve agri...@chromium.orgwrote: Great! I agree it's time someone take a stab at this! On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill stevengil...@gmail.com wrote: I want to try and flush out the process for merging the dev branches for the core plugins into master and get it onto the wiki. Currently the dev branches have some readme changes, namespace changes and package changes for android. I don't believe any of these changes should be breaking changes. Process 1. Create issue on jira for running mobile spec tests on all platforms using dev branch of plugins 2. Test on all platforms 3. Merge in change into master 4. Publish to plugins.cordova.io? Do we really need to test the plugins on all the platforms for changes that won't affect them at all? I think no. And we should only test plugins that have changes to them (in this case all of them). Should add in bumping of the version number. I think one thing to add to the process is to create mobilespec with the existing versions of plugins, then `cordova plugin rm` them all, then `cordova plugin add` the new ones using a URL that points to the dev branch. aka, test out the upgrade process.
