[ANNOUNCE] cordova-ios 4.1.1 released
cordova-ios@4.1.1 is on NPM now: https://www.npmjs.com/package/cordova-ios Check out blog post at https://cordova.apache.org/announcements/2016/04/04/ios-4.1.1.html and retweet https://twitter.com/apachecordova/status/718229585758986241 Thanks, Edna Morales
RE: [VOTE] 4.1.1 iOS Release - Take 2
The vote has now closed. The results are: Positive Binding Votes: 3 Edna Morales Jesse MacFadyen Alexander Sorokin The vote has passed. Thanks, Edna Morales From: "Alexander Sorokin (Akvelon)" To: "dev@cordova.apache.org" Date: 04/07/2016 12:28 PM Subject:RE: [VOTE] 4.1.1 iOS Release - Take 2 I vote +1: * Verified archives via `coho verify-archive` * Verified tags manually * Verified that blank app creates correctly with platform * Verified that blank app can be successfully ran and built * Verified that platform can be updated from previous version * Verified compatibility with core plugins (ran mobilespec for released and edge versions) * Checked for whitespace issues * Checked for Unicode issues * Verified version * Verified line breaks -Original Message- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Thursday, April 7, 2016 9:34 AM To: dev@cordova.apache.org Subject: Re: [VOTE] 4.1.1 iOS Release - Take 2 +1 - Ran coho audit-license-headers - Ran coho check-license - Ran coho verify archive - Ran iOS native tests > Good signature from "Edna Morales" - Created and ran hello world iOS app with CLI @purplecabbage https://na01.safelinks.protection.outlook.com/?url=risingj.com&data=01%7c01%7cv-alsoro%40microsoft.com%7c43edcedae49b4e6bbe3908d35eaeac46%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=zLJPSjVixkTXxCb0vsEXrFDyCp9rEpkwftmXmFhqanY%3d On Tue, Apr 5, 2016 at 10:51 AM, Edna Y Morales wrote: > > > Please review and vote on this 4.1.1 iOS Release by replying to this > email (and keep discussion on the DISCUSS thread) > > Release issue: > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue > s.apache.org%2fjira%2fbrowse%2fCB-11006&data=01%7c01%7cv-alsoro%40micr > osoft.com%7c43edcedae49b4e6bbe3908d35eaeac46%7c72f988bf86f141af91ab2d7 > cd011db47%7c1&sdata=LqBRu%2bX5RJDv3kscYEDYbtLxpcYxeGELZJtYobeaiME%3d > > The archive has been published to dist/dev: > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdist. > apache.org%2frepos%2fdist%2fdev%2fcordova%2fCB-11006%2f&data=01%7c01%7 > cv-alsoro%40microsoft.com%7c43edcedae49b4e6bbe3908d35eaeac46%7c72f988b > f86f141af91ab2d7cd011db47%7c1&sdata=IganzibFulOMsjHAJolq8UM6K5toA8g0N0 > aBSPG88hY%3d > > The package was published from its corresponding git tag: > cordova-ios: 4.1.1 (c5c33bad30) > > Note that you can test it out via: > > cordova platform add https://github.com/apache/cordova-ios#4.1.1 > > Upon a successful vote I will upload the archive to dist/, publish it > to npm, and post the blog post. > > Voting guidelines: > https://github.com/apache/cordova-coho/blob/master/docs/release-voting > .md > > Voting will go on for a minimum of 48 hours. > > I vote +1: > * Ran coho audit-license-headers over the relevant repos > * Ran coho check-license to ensure all dependencies and > subdependencies have Apache-compatible licenses > * Ensured continuous build was green when repo was tagged > * Ran mobile-spec (iOS) > * Created and ran hello world iOS app with CLI > * Created and ran hello world iOS app non-CLI > * Tested ./bin/create script > * Tested project upgrade from 4.1.0 to 4.1.1 with CLI > * Tested project upgrade from 4.1.0 to 4.1.1 non-CLI > * Ran cordova-lib tests > * Ran iOS native tests > * Ran coho verify-archive > > Thanks, > Edna Morales > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[VOTE] 4.1.1 iOS Release - Take 2
Please review and vote on this 4.1.1 iOS Release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-11006 The archive has been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-11006/ The package was published from its corresponding git tag: cordova-ios: 4.1.1 (c5c33bad30) Note that you can test it out via: cordova platform add https://github.com/apache/cordova-ios#4.1.1 Upon a successful vote I will upload the archive to dist/, publish it to npm, and post the blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ensured continuous build was green when repo was tagged * Ran mobile-spec (iOS) * Created and ran hello world iOS app with CLI * Created and ran hello world iOS app non-CLI * Tested ./bin/create script * Tested project upgrade from 4.1.0 to 4.1.1 with CLI * Tested project upgrade from 4.1.0 to 4.1.1 non-CLI * Ran cordova-lib tests * Ran iOS native tests * Ran coho verify-archive Thanks, Edna Morales
RE: [Vote] 4.1.1 iOS Release
The vote has failed. I will start a new vote thread in a few mins. Thanks, Edna Morales From: "Alexander Sorokin (Akvelon)" To: "dev@cordova.apache.org" Date: 04/05/2016 11:39 AM Subject:RE: [Vote] 4.1.1 iOS Release Adding a platform from the archive fails with message "Cannot find module 'underscore'". It looks like something Is missing from the archive. So, -1. Thanks, Alexander Sorokin -Original Message- From: Edna Y Morales [mailto:eymor...@us.ibm.com] Sent: Monday, April 4, 2016 8:45 PM To: dev@cordova.apache.org Subject: [Vote] 4.1.1 iOS Release Please review and vote on this 4.1.1 iOS Release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-11006&data=01%7c01%7cv-alsoro%40microsoft.com%7c169a92f8859542efa16308d35cb0e7e8%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=FgpI46hMAbijYmzBXddUP%2bdpuKZOCGKZ9CShMHBa%2bvA%3d The archive has been published to dist/dev: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdist.apache.org%2frepos%2fdist%2fdev%2fcordova%2fCB-11006%2f&data=01%7c01%7cv-alsoro%40microsoft.com%7c169a92f8859542efa16308d35cb0e7e8%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=3QPGuk9GYwRDGH%2f39hY9JMPM6OfsRHZ1NUn18CTvNrc%3d The package was published from its corresponding git tag: cordova-ios: 4.1.1 (c5c33bad30) Note that you can test it out via: cordova platform add https://github.com/apache/cordova-ios#4.1.1 Upon a successful vote I will upload the archive to dist/, publish it to npm, and post the blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ensured continuous build was green when repo was tagged * Ran mobile-spec (iOS) * Created and ran hello world iOS app with CLI * Created and ran hello world iOS app non-CLI * Tested ./bin/create script * Tested project upgrade from 4.1.0 to 4.1.1 with CLI * Tested project upgrade from 4.1.0 to 4.1.1 non-CLI * Ran cordova-lib tests * Ran iOS native tests * Ran coho verify-archive Thanks, Edna Morales - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] cordova-ios release
Thanks, Mefire! So there is an issue with the archive that I published on dist/dev. I don't see the issue when I install from git so it must be something in the packaging that I'll need to investigate. I'll close the vote as Failed, republish and restart the vote. Thanks, Edna Morales From: "Mefire O." To: "dev@cordova.apache.org" Date: 04/04/2016 02:02 PM Subject:RE: [DISCUSS] cordova-ios release LGTM! Thanks, Mefire From: Edna Y Morales [mailto:eymor...@us.ibm.com] Sent: Monday, April 4, 2016 10:47 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] cordova-ios release Can someone review the blog post? https://github.com/apache/cordova-docs/pull/571 Thanks, Edna Morales [Inactive hide details for Shazron ---03/30/2016 08:28:03 PM---Thanks Edna - appreciated :) On Wed, Mar 30, 2016 at 8:15 AM, Edn]Shazron ---03/30/2016 08:28:03 PM---Thanks Edna - appreciated :) On Wed, Mar 30, 2016 at 8:15 AM, Edna Y Morales mailto:eymor...@us.ibm.com>> w From: Shazron mailto:shaz...@gmail.com>> To: "dev@cordova.apache.org<mailto:dev@cordova.apache.org>" mailto:dev@cordova.apache.org>> Date: 03/30/2016 08:28 PM Subject: Re: [DISCUSS] cordova-ios release ____ Thanks Edna - appreciated :) On Wed, Mar 30, 2016 at 8:15 AM, Edna Y Morales mailto:eymor...@us.ibm.com>> wrote: > Hi, > > I'd like to drive the release for cordova-ios 4.1.1. Does anyone have any > oppositions or any reason to wait? > > Thanks, > *Edna Morales* > > [image: Inactive hide details for Edna Y Morales---03/24/2016 09:41:54 > AM---bump to this discussion since cordova-common has been relea]Edna Y > Morales---03/24/2016 09:41:54 AM---bump to this discussion since > cordova-common has been released Thanks, > > From: Edna Y Morales/Durham/IBM@IBMUS > To: dev@cordova.apache.org<mailto:dev@cordova.apache.org> > Date: 03/24/2016 09:41 AM > Subject: Re: [DISCUSS] cordova-ios release > -- > > > > bump to this discussion since cordova-common has been released > > Thanks, > *Edna Morales* > > Shazron ---03/18/2016 10:34:07 PM---Another issue, the bundled ios-sim > should be updated: *https://issues.apache.org/jira/browse/CB-10912* > <https://issues.apache.org/jira/browse/CB-10912< https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10912&data=01%7c01%7commenjik%40microsoft.com%7c245cd1554777444c794c08d35cb10aae%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=b2DfQhpWhLbsxXZEoWdT9hEPte9ex2zshJndNU8k0F4%3d >> > > From: Shazron mailto:shaz...@gmail.com>> > To: "dev@cordova.apache.org<mailto:dev@cordova.apache.org>" mailto:dev@cordova.apache.org>> > Date: 03/18/2016 10:34 PM > Subject: Re: [DISCUSS] cordova-ios release > -- > > > > Another issue, the bundled ios-sim should be updated: > *https://issues.apache.org/jira/browse/CB-10912* > <https://issues.apache.org/jira/browse/CB-10912< https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10912&data=01%7c01%7commenjik%40microsoft.com%7c245cd1554777444c794c08d35cb10aae%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=b2DfQhpWhLbsxXZEoWdT9hEPte9ex2zshJndNU8k0F4%3d >> > > On Thu, Mar 17, 2016 at 1:58 PM, Edna Y Morales mailto:eymor...@us.ibm.com>> > wrote: > > > Ok sounds good > > > > Thanks, > > *Edna Morales* > > > > [image: Inactive hide details for Carlos Santana ---03/17/2016 04:48:19 > > PM---I agree Steve - Carlos]Carlos Santana ---03/17/2016 04:48:19 PM---I > > agree Steve - Carlos > > > > From: Carlos Santana mailto:csantan...@gmail.com >> > > To: dev@cordova.apache.org<mailto:dev@cordova.apache.org> > > Date: 03/17/2016 04:48 PM > > Subject: Re: [DISCUSS] cordova-ios release > > -- > > > > > > > > I agree Steve > > > > - Carlos > > @csantanapr > > > > > On Mar 17, 2016, at 4:17 PM, Steven Gill mailto:stevengil...@gmail.com>> > wrote: > > > > > > Lets do a common release first and then follow that up with patch ios > > > release > > > > > >> On Thu, Mar 17, 2016 at 11:24 AM, Shazron mailto:shaz...@gmail.com>> wrote: > > >> > > >> I would say patch release. I had some items I wanted in the next > > >> release (labeled cordova-ios-4.1.1), but that shouldn't hold up > > >> releasing often, keep the train running... > > >> > > >> Ideally it should be accompanied with the patches I did yesterday f
Re: [DISCUSS] cordova-ios release
Can someone review the blog post? https://github.com/apache/cordova-docs/pull/571 Thanks, Edna Morales From: Shazron To: "dev@cordova.apache.org" Date: 03/30/2016 08:28 PM Subject:Re: [DISCUSS] cordova-ios release Thanks Edna - appreciated :) On Wed, Mar 30, 2016 at 8:15 AM, Edna Y Morales wrote: > Hi, > > I'd like to drive the release for cordova-ios 4.1.1. Does anyone have any > oppositions or any reason to wait? > > Thanks, > *Edna Morales* > > [image: Inactive hide details for Edna Y Morales---03/24/2016 09:41:54 > AM---bump to this discussion since cordova-common has been relea]Edna Y > Morales---03/24/2016 09:41:54 AM---bump to this discussion since > cordova-common has been released Thanks, > > From: Edna Y Morales/Durham/IBM@IBMUS > To: dev@cordova.apache.org > Date: 03/24/2016 09:41 AM > Subject: Re: [DISCUSS] cordova-ios release > -- > > > > bump to this discussion since cordova-common has been released > > Thanks, > *Edna Morales* > > Shazron ---03/18/2016 10:34:07 PM---Another issue, the bundled ios-sim > should be updated: *https://issues.apache.org/jira/browse/CB-10912* > <https://issues.apache.org/jira/browse/CB-10912> > > From: Shazron > To: "dev@cordova.apache.org" > Date: 03/18/2016 10:34 PM > Subject: Re: [DISCUSS] cordova-ios release > -- > > > > Another issue, the bundled ios-sim should be updated: > *https://issues.apache.org/jira/browse/CB-10912* > <https://issues.apache.org/jira/browse/CB-10912> > > On Thu, Mar 17, 2016 at 1:58 PM, Edna Y Morales > wrote: > > > Ok sounds good > > > > Thanks, > > *Edna Morales* > > > > [image: Inactive hide details for Carlos Santana ---03/17/2016 04:48:19 > > PM---I agree Steve - Carlos]Carlos Santana ---03/17/2016 04:48:19 PM---I > > agree Steve - Carlos > > > > From: Carlos Santana > > To: dev@cordova.apache.org > > Date: 03/17/2016 04:48 PM > > Subject: Re: [DISCUSS] cordova-ios release > > -- > > > > > > > > I agree Steve > > > > - Carlos > > @csantanapr > > > > > On Mar 17, 2016, at 4:17 PM, Steven Gill > wrote: > > > > > > Lets do a common release first and then follow that up with patch ios > > > release > > > > > >> On Thu, Mar 17, 2016 at 11:24 AM, Shazron wrote: > > >> > > >> I would say patch release. I had some items I wanted in the next > > >> release (labeled cordova-ios-4.1.1), but that shouldn't hold up > > >> releasing often, keep the train running... > > >> > > >> Ideally it should be accompanied with the patches I did yesterday for > > >> cordova-common (since cordova-common is bundled in to cordova-ios), > > >> but those bugs only really affect cordova-cli functionality > > >> > > >> On Thu, Mar 17, 2016 at 11:09 AM, Edna Y Morales > > > >> wrote: > > >>> > > >>> Hi, > > >>> > > >>> We are interested in a cordova-ios release, specifically for this > jira > > >>> item: *https://issues.apache.org/jira/browse/CB-10773* > <https://issues.apache.org/jira/browse/CB-10773> > > >>> > > >>> Is there any opposition to this or any reason to wait? Steve would it > > >> make > > >>> sense to wait for a cordova-common release to happen first, before > > doing > > >>> the cordova-ios release? > > >>> > > >>> Would it be a patch release or a minor release? > > >>> > > >>> Thanks, > > >>> Edna Morales > > >> > > >> - > > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > >> For additional commands, e-mail: dev-h...@cordova.apache.org > > >> > > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > > > >
[Vote] 4.1.1 iOS Release
Please review and vote on this 4.1.1 iOS Release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-11006 The archive has been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-11006/ The package was published from its corresponding git tag: cordova-ios: 4.1.1 (c5c33bad30) Note that you can test it out via: cordova platform add https://github.com/apache/cordova-ios#4.1.1 Upon a successful vote I will upload the archive to dist/, publish it to npm, and post the blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ensured continuous build was green when repo was tagged * Ran mobile-spec (iOS) * Created and ran hello world iOS app with CLI * Created and ran hello world iOS app non-CLI * Tested ./bin/create script * Tested project upgrade from 4.1.0 to 4.1.1 with CLI * Tested project upgrade from 4.1.0 to 4.1.1 non-CLI * Ran cordova-lib tests * Ran iOS native tests * Ran coho verify-archive Thanks, Edna Morales
Re: [VOTE] Tools release attempt 2
I vote +1 -Verified tags for all 3 tools with coho verify-tags -Tested hello world app with ios and android and all core plugins installed -Created hello world app with windows and all core plugins installed, but did not run on device or emulator Thanks, Edna Morales From: Carlos Santana To: "dev@cordova.apache.org" Date: 03/30/2016 06:10 PM Subject:Re: [VOTE] Tools release attempt 2 I vote +1 coho verify-archive vote-6.1.1/cordova-6.1.1.tgz coho verify-archive vote-6.1.1/cordova-lib-6.1.1.tgz coho verify-archive vote-6.1.1/plugman-1.2.1.tgz verify tag for cordova-plugman 6.1.1 was not able to verify tags for lib and cli, no problem with release content and signatures, just the tags need to be updated in the git repo cordova-cli tag 6.1.1 needs to be move to hash 8e730ac376 cordova-lib tag 6.1.1 needs to be move to hash 107e273647 Also cordova-cli master doesn't have latest commits from 8e730ac376 Tested hello-world app with ios and android $ coho verify-tags Running from /Users/csantana23/Documents/dev/cordova Paste in print-tags output then hit Enter cordova-lib: 6.1.1 (107e273647) cordova-lib: Hashes don't match! $ coho verify-tags Running from /Users/csantana23/Documents/dev/cordova Paste in print-tags output then hit Enter cordova-cli: 6.1.1 (8e730ac376) cordova-cli: Hashes don't match! On Tue, Mar 29, 2016 at 10:33 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > Please review and vote on this Tools Release by replying to this email > (and keep discussion on the DISCUSS thread) > > Release issue: https://issues.apache.org/jira/browse/CB-10980 > Both tools have been published to dist/dev: > https://dist.apache.org/repos/dist/dev/cordova/CB-10980 > > The packages were published from their corresponding git tags: > cordova-lib: 6.1.1 (107e273647) > cordova-plugman: 1.2.1 (f05a7ef8cf) > cordova-cli: 6.1.1 (8e730ac376) > > Upon a successful vote I will upload the archives to dist/, publish them > to NPM, and post the corresponding blog post. > > Voting guidelines: > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md > > Voting will go on for a minimum of 48 hours. > > I vote +1: > * Ran coho audit-license-headers over the relevant repos > * Ran coho check-license to ensure all dependencies and subdependencies > have Apache-compatible licenses > * Ensured continuous build was green when repos were tagged > * Created and ran mobilespec app on Android and Windows > * Ran mobilespec app with --browserify flag on Android > * Ensured unit tests are passing for cli, lib and plugman > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: [DISCUSS] cordova-ios release
Hi, I'd like to drive the release for cordova-ios 4.1.1. Does anyone have any oppositions or any reason to wait? Thanks, Edna Morales From: Edna Y Morales/Durham/IBM@IBMUS To: dev@cordova.apache.org Date: 03/24/2016 09:41 AM Subject:Re: [DISCUSS] cordova-ios release bump to this discussion since cordova-common has been released Thanks, Edna Morales Shazron ---03/18/2016 10:34:07 PM---Another issue, the bundled ios-sim should be updated: https://issues.apache.org/jira/browse/CB-10912 From: Shazron To: "dev@cordova.apache.org" Date: 03/18/2016 10:34 PM Subject: Re: [DISCUSS] cordova-ios release Another issue, the bundled ios-sim should be updated: https://issues.apache.org/jira/browse/CB-10912 On Thu, Mar 17, 2016 at 1:58 PM, Edna Y Morales wrote: > Ok sounds good > > Thanks, > *Edna Morales* > > [image: Inactive hide details for Carlos Santana ---03/17/2016 04:48:19 > PM---I agree Steve - Carlos]Carlos Santana ---03/17/2016 04:48:19 PM---I > agree Steve - Carlos > > From: Carlos Santana > To: dev@cordova.apache.org > Date: 03/17/2016 04:48 PM > Subject: Re: [DISCUSS] cordova-ios release > -- > > > > I agree Steve > > - Carlos > @csantanapr > > > On Mar 17, 2016, at 4:17 PM, Steven Gill wrote: > > > > Lets do a common release first and then follow that up with patch ios > > release > > > >> On Thu, Mar 17, 2016 at 11:24 AM, Shazron wrote: > >> > >> I would say patch release. I had some items I wanted in the next > >> release (labeled cordova-ios-4.1.1), but that shouldn't hold up > >> releasing often, keep the train running... > >> > >> Ideally it should be accompanied with the patches I did yesterday for > >> cordova-common (since cordova-common is bundled in to cordova-ios), > >> but those bugs only really affect cordova-cli functionality > >> > >> On Thu, Mar 17, 2016 at 11:09 AM, Edna Y Morales > >> wrote: > >>> > >>> Hi, > >>> > >>> We are interested in a cordova-ios release, specifically for this jira > >>> item: https://issues.apache.org/jira/browse/CB-10773 > >>> > >>> Is there any opposition to this or any reason to wait? Steve would it > >> make > >>> sense to wait for a cordova-common release to happen first, before > doing > >>> the cordova-ios release? > >>> > >>> Would it be a patch release or a minor release? > >>> > >>> Thanks, > >>> Edna Morales > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> For additional commands, e-mail: dev-h...@cordova.apache.org > >> > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
Re: [DISCUSS] cordova-ios release
bump to this discussion since cordova-common has been released Thanks, Edna Morales From: Shazron To: "dev@cordova.apache.org" Date: 03/18/2016 10:34 PM Subject:Re: [DISCUSS] cordova-ios release Another issue, the bundled ios-sim should be updated: https://issues.apache.org/jira/browse/CB-10912 On Thu, Mar 17, 2016 at 1:58 PM, Edna Y Morales wrote: > Ok sounds good > > Thanks, > *Edna Morales* > > [image: Inactive hide details for Carlos Santana ---03/17/2016 04:48:19 > PM---I agree Steve - Carlos]Carlos Santana ---03/17/2016 04:48:19 PM---I > agree Steve - Carlos > > From: Carlos Santana > To: dev@cordova.apache.org > Date: 03/17/2016 04:48 PM > Subject: Re: [DISCUSS] cordova-ios release > -- > > > > I agree Steve > > - Carlos > @csantanapr > > > On Mar 17, 2016, at 4:17 PM, Steven Gill wrote: > > > > Lets do a common release first and then follow that up with patch ios > > release > > > >> On Thu, Mar 17, 2016 at 11:24 AM, Shazron wrote: > >> > >> I would say patch release. I had some items I wanted in the next > >> release (labeled cordova-ios-4.1.1), but that shouldn't hold up > >> releasing often, keep the train running... > >> > >> Ideally it should be accompanied with the patches I did yesterday for > >> cordova-common (since cordova-common is bundled in to cordova-ios), > >> but those bugs only really affect cordova-cli functionality > >> > >> On Thu, Mar 17, 2016 at 11:09 AM, Edna Y Morales > >> wrote: > >>> > >>> Hi, > >>> > >>> We are interested in a cordova-ios release, specifically for this jira > >>> item: https://issues.apache.org/jira/browse/CB-10773 > >>> > >>> Is there any opposition to this or any reason to wait? Steve would it > >> make > >>> sense to wait for a cordova-common release to happen first, before > doing > >>> the cordova-ios release? > >>> > >>> Would it be a patch release or a minor release? > >>> > >>> Thanks, > >>> Edna Morales > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> For additional commands, e-mail: dev-h...@cordova.apache.org > >> > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
Re: [DISCUSS] cordova-ios release
Ok sounds good Thanks, Edna Morales From: Carlos Santana To: dev@cordova.apache.org Date: 03/17/2016 04:48 PM Subject:Re: [DISCUSS] cordova-ios release I agree Steve - Carlos @csantanapr > On Mar 17, 2016, at 4:17 PM, Steven Gill wrote: > > Lets do a common release first and then follow that up with patch ios > release > >> On Thu, Mar 17, 2016 at 11:24 AM, Shazron wrote: >> >> I would say patch release. I had some items I wanted in the next >> release (labeled cordova-ios-4.1.1), but that shouldn't hold up >> releasing often, keep the train running... >> >> Ideally it should be accompanied with the patches I did yesterday for >> cordova-common (since cordova-common is bundled in to cordova-ios), >> but those bugs only really affect cordova-cli functionality >> >> On Thu, Mar 17, 2016 at 11:09 AM, Edna Y Morales >> wrote: >>> >>> Hi, >>> >>> We are interested in a cordova-ios release, specifically for this jira >>> item: https://issues.apache.org/jira/browse/CB-10773 >>> >>> Is there any opposition to this or any reason to wait? Steve would it >> make >>> sense to wait for a cordova-common release to happen first, before doing >>> the cordova-ios release? >>> >>> Would it be a patch release or a minor release? >>> >>> Thanks, >>> Edna Morales >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> For additional commands, e-mail: dev-h...@cordova.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[DISCUSS] cordova-ios release
Hi, We are interested in a cordova-ios release, specifically for this jira item: https://issues.apache.org/jira/browse/CB-10773 Is there any opposition to this or any reason to wait? Steve would it make sense to wait for a cordova-common release to happen first, before doing the cordova-ios release? Would it be a patch release or a minor release? Thanks, Edna Morales
RE: [VOTE] Plugins Release camera@2.1.1 globalization@1.0.3 splashscreen@3.2.1 statusbar@2.1.2
+1 * Ran mobilespec plugin tests (ios) * Verified that hello world app be can built and run with plugins (ios) * Verified tags with 'coho verify-tags' Thanks, Edna Morales From: "Alexander Sorokin (Akvelon)" To: "dev@cordova.apache.org" Date: 03/10/2016 05:20 AM Subject:RE: [VOTE] Plugins Release camera@2.1.1 globalization@1.0.3 splashscreen@3.2.1 statusbar@2.1.2 I vote +1. * Verified signatures and hashes * Verified tags * Verified that plugins can be added correctly to blank app * Verified that blank app can be successfully built and ran (windows and android) * Verified that browserified app can be successfully built and ran (windows and android) * Ran smoke testing of mobilespec app (windows and android) * Verified release notes -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Thursday, March 10, 2016 6:59 AM To: dev@cordova.apache.org Subject: [VOTE] Plugins Release camera@2.1.1 globalization@1.0.3 splashscreen@3.2.1 statusbar@2.1.2 Please review and vote on the release of this plugins release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10820&data=01%7c01%7cv-alsoro%40microsoft.com%7c3bb1f1c33f834014cb0308d348985372%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=KzCVERC8MyeVLeVpWIcRSl7gTsv524%2fdYEr%2bi8t1450%3d The plugins have been published to dist/dev: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdist.apache.org%2frepos%2fdist%2fdev%2fcordova%2fCB-10820%2f&data=01%7c01%7cv-alsoro%40microsoft.com%7c3bb1f1c33f834014cb0308d348985372%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=NA3rwF0RFbHpxo9nxYHPAwKggnKk3d5ORuKcL%2bAwkas%3d The packages were published from their corresponding git tags: cordova-plugin-camera: 2.1.1 (37dd471d0e) cordova-plugin-statusbar: 2.1.2 (f1aa062557) cordova-plugin-globalization: 1.0.3 (37c3e61e12) cordova-plugin-splashscreen: 3.2.1 (e877722bac) Upon a successful vote I will upload the archives to dist/, upload them to the Plugins Registry, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ran mobilespec with new plugins - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Plugins release
bump Thanks, Edna Morales From: julio cesar sanchez To: "dev@cordova.apache.org" Date: 03/04/2016 02:52 PM Subject:Re: [DISCUSS] Plugins release cordova-plugin-camera should be released too, right now picking images from the gallery doesn't work on android 4.4+ 2016-03-04 19:42 GMT+01:00 Edna Y Morales : > > Hi, > > There are some fixes we are wanting to get released for > cordova-plugin-globalization and cordova-plugin-splashscreen. Any thoughts > on when we can do the next release for these? > > For cordova-plugin-globalization there are several deprecation warnings > that we need to get rid of. Addressed by > https://issues.apache.org/jira/browse/CB-10605 > > For cordova-plugin-splashscreen there is also a deprecation warning. > Addressed by https://issues.apache.org/jira/browse/CB-10606 > > Thanks, > Edna Morales >
[DISCUSS] Plugins release
Hi, There are some fixes we are wanting to get released for cordova-plugin-globalization and cordova-plugin-splashscreen. Any thoughts on when we can do the next release for these? For cordova-plugin-globalization there are several deprecation warnings that we need to get rid of. Addressed by https://issues.apache.org/jira/browse/CB-10605 For cordova-plugin-splashscreen there is also a deprecation warning. Addressed by https://issues.apache.org/jira/browse/CB-10606 Thanks, Edna Morales
Globalization and Splashscreen plugins release
Hi, There are some fixes we are wanting to get released for cordova-plugin-globalization and cordova-plugin-splashscreen. Any thoughts on when we can do the next release for these? Thanks, Edna Morales
CB-9901 cordova plugin search opens in a browser
Hi all, I have made a change to have the cordova plugin search command open the browser to 'http://cordova.apache.org/plugins/?q='. Nikhil has reviewed the changes already and they look good. But I just wanted to make sure the community is good with this change before I merge it in. Thanks, Edna
iOS 9 testing
Hi all, I've been doing some iOS 9 testing. I'm not seeing any issues when running mobilespec. Although, I know there is a jira item for having the tags in the whitelist work for ATS. I'm bypassing that for now and everything looks good on the UIWebView. Once adding the WKWebView I am seeing about 7 failures in the auto tests dealing with contacts, XHR requests and session storage. I'm not sure if Shaz is aware of these but if not I can create a jira item for them. Just wanted to give my update. Thanks, Edna
WKWebView and iOS 9
Hi all, Since the file:// url loading bug was fixed for WKWebView in iOS 9, are we going to move away from the local webserver solution? Thanks, Edna Morales
Re: Question about plugin/platform --save: src vs version?
It could make sense to store both for the case where restoring from src fails. For example, if the path to a local folder no longer exists, what do you use to restore? In that case you could use the version as a fallback? Thanks, Edna Morales From: "Gorkem Ercan" To: "dev [dev@cordova.apache.org]" Date: 03/30/2015 10:45 AM Subject:Re: Question about plugin/platform --save: src vs version? On 29 Mar 2015, at 23:11, Tim Barham wrote: > Hi - I'm looking for input on this issue: For the plugin/platform > --save feature, there's currently an inconsistency between how we > store the information in config.xml for platforms vs plugins. > > > > For platforms, we have a 'version' attribute where we store either the > source location or the version: if the platform was added by > specifying a specific location (git repository, local folder, package > file etc), we store that in the 'version' attribute. Otherwise we > store the actual version. > > > > For plugins, these two values are stored separately - source location > in the 'src' attribute and version in the 'version' attribute. Note > however that when we restore a plugin, we ignore the 'version' > attribute if there is a 'src' attribute. > > This comes from the history of the implementation ( as these things do). In the old experimental save implementation, we had 3 parameters, namely, version, url and installPath, and for every plugin we expected one of them to exist. During the effort for npmizing the save functionality the contribution for platforms and plugins were done separately hence the unmatching attributes. So there is no real technical reason for doing one way or the other and if you are willing to unify them that is fantastic. > > I'd like to make these consistent. My first thought was to support > 'version' and 'src' for platforms like we currently do for plugins. > But since we always ignore the version if we have a src, I'm not sure > we actually gain anything by doing that. Storing them in different > attributes is perhaps clearer, but storing both implies we make use of > both, which we don't. Also, the code ends up being simpler overall if > we just store whichever we care about in the version attribute. > I personally prefer to clearly label data in case user needs to read/modify the config.xml, seeing a git url on the version attribute still puzzles me. But I am fine with either way. Whatever you decide please remember to support/migrate the current attributes so that we do not end up with stale entries on config.xml > > > Any thoughts either way? > > > > Thanks! > > > > Tim - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
iOS 8.3 beta 4
Very minor changes according to the release notes and API diffs but ran through mobilespec anyway and everything looks good. Thanks, Edna Morales
Re: 'cordova plugin save' should also save plugin versions
Ah yes. Looks like it. Thanks, Edna Morales From: Raymond Camden To: dev@cordova.apache.org Date: 03/24/2015 11:30 AM Subject:Re: 'cordova plugin save' should also save plugin versions Is that a dupe of https://issues.apache.org/jira/browse/CB-8594? On Tue, Mar 24, 2015 at 10:19 AM, Edna Y Morales wrote: > > > Currently, version info is not saved for plugins in the fetch.json. That > needs to be added so that plugin version can be saved in the config.xml. It > should follow what 'cordova platform save' does. I created a jira item for > this: https://issues.apache.org/jira/browse/CB-8733 and opened a pull > request: https://github.com/apache/cordova-lib/pull/189. If someone could > review it and provide any feedback. > > Thanks, > Edna Morales -- === Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
'cordova plugin save' should also save plugin versions
Currently, version info is not saved for plugins in the fetch.json. That needs to be added so that plugin version can be saved in the config.xml. It should follow what 'cordova platform save' does. I created a jira item for this: https://issues.apache.org/jira/browse/CB-8733 and opened a pull request: https://github.com/apache/cordova-lib/pull/189. If someone could review it and provide any feedback. Thanks, Edna Morales
iOS 8.3 beta 3 testing
Did regression testing for iOS 8.3 beta 3 and saw no issues. Thanks, Edna Morales
Tested iOS 8.3 beta 2
No regressions were seen. FYI Thanks, Edna Morales
iOS 8.3 beta testing
Ran through the auto and manual tests for iOS 8.3 beta and saw no regressions. FYI Thanks, Edna Morales
[iOS] Possible Cordova bug with WebSocket in plugin callback
Hi all, I'm working on a bug that was reported for iOS (not through Jira), and I'm running out of ideas on figuring out what is going on. So I'm reaching out to the dev list to see if anyone can provide insight or thoughts on what may be going on. The use case is this: 1. Call navigator.geolocation.getCurrentPosition(success, error); 2. Inside the success callback, open a websocket. 3. Inside websocket.onopen event handler, have a for loop that runs 20,000 times. Inside the for loop send a message to the websocket, increment a counter, and update an element in the DOM with the new count. The crash happens on the DOM update inside of the for loop. If I move the websocket code outside of the plugin callback, the crash is not seen. If I append a new element to the DOM instead of updating the same element, the crash is not seen. If I switch out the Cordova geolocation plugin for the native one, the crash is not seen. I have tried a few other scenarios but can't pinpoint anything. The crash is happening on the WebThread and sometimes I get this message "[CFRunLoopTimer release:]: message sent to deallocated instance 0x174370c80". The stack trace doesn't trace back to anything specific to Cordova code. It's from the WebCore. It seems like it could just be a bug in WebKit, but some of the scenarios mentioned above also make that hard to verify. If anyone has any insight on this, it would be great. Let me know if you need anymore details. Thanks, Edna Morales
iOS 8.1.3
Apple recently released a minor update (iOS 8.1.3). No issues were found on Cordova. FYI Thanks, Edna Morales
iOS 8.2 beta 3 out
iOS 8.2 beta 3 is out. I have ran the mobilespec tests and did not find any issues. Just FYI Thanks, Edna
Re: cordova xxx add - is there a problem?
I have started doing some work on this. Currently "platform add" does a check to see if the OS supports the platform. If it does not, then it just automatically throws an error without attempting to add it. I have changed this to just print out a warning message and continue with the process. The "prepare" command does not seem to be giving me any issues when I add a platform for which the environment is not set up so I think it's safe to leave that. The next issue is to be sure that the platform's "check_reqs" is not getting called within the platform's create script. For Android, I believe that was removed recently. Windows does not call it and I am currently working on converting the iOS bash scripts to nodejs in which I have removed the call to check_reqs. The check_reqs shouldn't be necessary until you build and run. The other thing to consider is what happens when you try to build using the CLI for a platform that you don't have the environment set up for. Currently, what I have implemented is that it will just end the process with an error on the first platform it hits that cannot be built. It will not try to build the remaining platforms. For example, if you are on a windows machine and you do "build ios android", it's going to error out when it try to build iOS and just end the process there. This is to avoid running the after_build hooks and to let the user know that they can't build for iOS. The idea there is that the user would skip building iOS and just do "build android". That is what I have so far and am open to any feedback or suggestions. My first priority is to get the iOS scripts converted to nodejs so that the iOS platform can be added even if you are on a nonsupported OS. Thanks, Edna Morales From: Marcel Kinard To: dev@cordova.apache.org Date: 11/03/2014 05:07 PM Subject:Re: cordova xxx add - is there a problem? Edna is doing some work in this area. https://issues.apache.org/jira/browse/CB-7803 On Nov 3, 2014, at 4:33 PM, Treggiari, Leo wrote: >> I think you would like for each developer to be able to be able to work on any project regardless of locally available sdks, correct? > > Yes. Thanks.
Re: Adding ability to add any platform on any OS
Thanks for the feedback everyone. I'm not seeing anything in the scripts that require an environment to be set up other than compile and run, which check the environment requirements. Maybe user added hooks would cause issues. Adding a plugin seems to copy files into the project's platforms and add references in XML files or keys in the plist file if necessary. But perhaps I am missing something here? If it is not ideal to change the workflow then maybe the suggested --force flag could be an alternative? Thanks, Edna Morales From: Gorkem Ercan To: "dev@cordova.apache.org" Date: 10/18/2014 11:46 AM Subject:Re: Adding ability to add any platform on any OS On Sat, Oct 18, 2014 at 06:22:12AM +, Parashuram Narasimhan (MS OPEN TECH) wrote: > What about saving and restoring platforms? Cordova platforms will not be checked in, but we could do a cordova platform save. When I now do a cordova platform restore on my Mac machine, will is try to restore the Windows platform also and fail ? > "cordova restore platforms" will not be able to restore windows on a Mac, it basically delegates to "cordova add" which will fail. Unfortunately, it will stop platform restoration after first failed platform which I think should not be the case [1]. I think the ultimate goal with cordova restore is to make it part of the prepare cycle and remove plugins and platforms folders. In such a setting restoring platforms that we can not cater on a host OS will probably cause more harm. I can see some cases where this could be a useful feature but I do not think they are part of the main flow. Perhaps a --force flag can be added for this one? [1] https://issues.apache.org/jira/browse/CB-7820 -- Gorkem > -Original Message- > From: Josh Soref [mailto:jso...@blackberry.com] > Sent: Friday, October 17, 2014 2:15 PM > To: Jesse; dev@cordova.apache.org > Subject: Re: Adding ability to add any platform on any OS > > cordova serve could still benefit from it... > > Although I haven't looked into it too much. Sent from my BlackBerry 10 smartphone. > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Adding ability to add any platform on any OS
Well the idea is that you should be able to add a platform to your project even if you can't build it. So that you can have multiple developers on different OS's working on the same project using SCM. That way, for example, you can add the Windows platform on OSX and just have another developer on a Windows machine build it. Thanks, Edna Morales From: Jesse To: "dev@cordova.apache.org" Date: 10/17/2014 04:31 PM Subject:Re: Adding ability to add any platform on any OS I don't see a ton of value in this, but I do see a lot of risk. Platform scripts + hooks are called for any changes to plugins (add/rm) so you are going to have multiple points of failure. Who does this feature help? @purplecabbage risingj.com On Fri, Oct 17, 2014 at 1:09 PM, Edna Y Morales wrote: > > > Hi all, > > I'm working on allowing the CLI to add any platform regardless of whether > the OS supports it. Basically you would add the platform, get a warning > stating that you won't be able to build for that platform, and then just > throw an error when an attempt to build is made. While looking into this, > I've noticed that there are checks in multiple places that are preventing > this. The first one is the check in cordova-lib that verifies the OS > supports the platform. I am changing that to give a warning to the user > instead of throwing an error. Then the check_reqs script for individual > platforms is called both in the create script and the build script. I'm > wondering if the check is required in the create script, when it's just > going to get called again in the build script. My plan is to remove the > check from the create script if there is nothing in there that requires a > platform specific environment. > > Any comments or feedback would be appreciated. > > Thanks, > Edna Morales
Adding ability to add any platform on any OS
Hi all, I'm working on allowing the CLI to add any platform regardless of whether the OS supports it. Basically you would add the platform, get a warning stating that you won't be able to build for that platform, and then just throw an error when an attempt to build is made. While looking into this, I've noticed that there are checks in multiple places that are preventing this. The first one is the check in cordova-lib that verifies the OS supports the platform. I am changing that to give a warning to the user instead of throwing an error. Then the check_reqs script for individual platforms is called both in the create script and the build script. I'm wondering if the check is required in the create script, when it's just going to get called again in the build script. My plan is to remove the check from the create script if there is nothing in there that requires a platform specific environment. Any comments or feedback would be appreciated. Thanks, Edna Morales
Re: Whitelist Test case failing in Mobilespec 3.6.3
Actually it looks like it was already fixed on master. But the issue was
with the test case itself.
Thanks,
Edna Morales
From: Edna Y Morales/Durham/IBM@IBMUS
To: dev@cordova.apache.org
Date: 10/15/2014 09:13 AM
Subject:Re: Whitelist Test case failing in Mobilespec 3.6.3
I submitted a pull request to fix this test case, but it has not been
merged in yet. Although now it has merge conflicts that I need to resolve
before it can get pulled in.
https://github.com/apache/cordova-mobile-spec/pull/107
Thanks,
Edna Morales
"Joshi, Pavankumar" ---10/14/2014 09:12:52 PM---Hello devs, I am currently
testing mobilespec 3.6.3 and I found a test case failing in whitelist.
From: "Joshi, Pavankumar"
To: "dev@cordova.apache.org"
Date: 10/14/2014 09:12 PM
Subject: Whitelist Test case failing in Mobilespec 3.6.3
Hello devs,
I am currently testing mobilespec 3.6.3 and I found a test case failing in
whitelist.
The test case is written like
itShouldMatch('file:///foo.html', [ ]);
As I understand that a new whitelist URL file:///foo.html<
file:///\\foo.html> is added and then tested for the pattern "[]". The API
whitelist.isUrlWhiteListed(url); returns false which means that blank
patterns are not allowed.
But the test cases expects the return value to be true. Hence the test case
fails.
Now is it the mistake of the test case or the API? What should I do to make
this test case pass?
Please can you tell me where is an explanation about Whitelist "match" and
"test" API explained and what does a pattern stand for?
Thanks in advance
Thanks and Regards
Pavan Joshi
Re: Whitelist Test case failing in Mobilespec 3.6.3
I submitted a pull request to fix this test case, but it has not been
merged in yet. Although now it has merge conflicts that I need to resolve
before it can get pulled in.
https://github.com/apache/cordova-mobile-spec/pull/107
Thanks,
Edna Morales
From: "Joshi, Pavankumar"
To: "dev@cordova.apache.org"
Date: 10/14/2014 09:12 PM
Subject:Whitelist Test case failing in Mobilespec 3.6.3
Hello devs,
I am currently testing mobilespec 3.6.3 and I found a test case failing in
whitelist.
The test case is written like
itShouldMatch('file:///foo.html', [ ]);
As I understand that a new whitelist URL file:///foo.html<
file:///\\foo.html> is added and then tested for the pattern "[]". The API
whitelist.isUrlWhiteListed(url); returns false which means that blank
patterns are not allowed.
But the test cases expects the return value to be true. Hence the test case
fails.
Now is it the mistake of the test case or the API? What should I do to make
this test case pass?
Please can you tell me where is an explanation about Whitelist "match" and
"test" API explained and what does a pattern stand for?
Thanks in advance
Thanks and Regards
Pavan Joshi
iOS 8.1 testing
I have gone through the mobilespec tests on 8.1 beta 2 and so far everything is looking good. Looks like the only API diffs are methods and constants that got added. Thanks, Edna Morales
Android L Testing
Hi all, I've done testing on mobilespec over Android L. Comparing against test results for Android 4.4.4, I'm not seeing any breakages on Android L. I'm not sure if anyone else has done testing that can confirm my findings, but just wanted to share what I found. Thanks, Edna Morales
Re: [iOS] ViewController whitelist visibility to command delegate
I actually discovered something that no longer requires this to be done. So nevermind. Thanks, Edna Morales From: Edna Y Morales/Durham/IBM@IBMUS To: cordova Date: 09/04/2014 12:11 PM Subject:[iOS] ViewController whitelist visibility to command delegate Hi all, I am trying to get visibility of the view controller whitelist in the cordova-plugin-whitelist so that the whitelist tests that are run can be compared against the view controller whitelist instead of a whitelist with only the given patterns provided in the tests themselves. One way I can tell to do it, is to add a view controller whitelist reference in the CDVCommandDelegate (like there is one for settings). I don't really see an issue with this since it is readonly, but I was hoping to get some feedback on whether this is the right thing to do or if I should go about it a different way. Thanks, Edna Morales
[iOS] ViewController whitelist visibility to command delegate
Hi all, I am trying to get visibility of the view controller whitelist in the cordova-plugin-whitelist so that the whitelist tests that are run can be compared against the view controller whitelist instead of a whitelist with only the given patterns provided in the tests themselves. One way I can tell to do it, is to add a view controller whitelist reference in the CDVCommandDelegate (like there is one for settings). I don't really see an issue with this since it is readonly, but I was hoping to get some feedback on whether this is the right thing to do or if I should go about it a different way. Thanks, Edna Morales
Re: [Discuss] 3.6.0 Release
There are a few issues on iOS (CB-7423). Thanks, Edna Morales From: Marcel Kinard To: dev@cordova.apache.org Date: 08/29/2014 12:10 PM Subject:Re: [Discuss] 3.6.0 Release So to consolidate the list of known issues that should be addressed before cutting an RC: * CB-7375 Investigate breaking changes at file plugin * Android manual plugin tests not run yet * CB-7410 lots of breakages of the Android native tests * CB-7416 Windows+plugins. source-file is not correctly processed Any omissions or extras? On Aug 27, 2014, at 2:19 PM, Sergey Grebnov (Akvelon) wrote: > Found out another Windows issue. Jesse could you pls take a look? Otherwise I'll investigate it my tomorrow morning. > > CB-7416 - Windows+plugins. source-file is not correctly processed > > Thx! > Sergey
Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of)
Yes no problem. I have created a Jira issue (CB-7423). Thanks, Edna Morales From: Marcel Kinard To: dev@cordova.apache.org Date: 08/28/2014 05:48 PM Subject:Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of) Edna, could you post the specific failures here or in a Jira item? (Not all 40 when run in aggregate since there are lots of false failures, but the few true failures when run in isolation.) Would be nice to get these fixed before 3.6.0 is cut. Thanks! On Aug 28, 2014, at 4:58 PM, Edna Y Morales wrote: > So I was still getting 40 or so failures on iOS when running mobilespec, even after updating jasmine. I ran the automatic tests for each plugin individually and doing that I get 3 file-transfer failures. For file, I get 2 copyTo failures only after running the tests a second time. I will update with the results of the plugin manual tests. > > For the native auto tests, I am seeing 1 whitelist failure. >
Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of)
So I was still getting 40 or so failures on iOS when running mobilespec, even after updating jasmine. I ran the automatic tests for each plugin individually and doing that I get 3 file-transfer failures. For file, I get 2 copyTo failures only after running the tests a second time. I will update with the results of the plugin manual tests. For the native auto tests, I am seeing 1 whitelist failure. Thanks, Edna Morales From: Carlos Santana To: "dev@cordova.apache.org" Date: 08/28/2014 12:34 PM Subject:Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of) Is the Google team switching to the new style tests for their Medic CI environment? On Thu, Aug 28, 2014 at 6:37 AM, Marcel Kinard wrote: > Very good news. > > I'm still left wondering why these failures are being discovered just now. > Are we all lacking that much discipline in running tests as we make commits? > > On Aug 27, 2014, at 9:24 PM, Michal Mocny wrote: > > > Awesome :P Sometimes you get lucky ;) > > > > > > On Wed, Aug 27, 2014 at 8:50 PM, Edna Y Morales > wrote: > > > >> Running only the file plugin tests, updating the version of jasmine in > the > >> assets brought the failures down from 16 to 0. Thanks for the suggestion > >> Michal! > > -- Carlos Santana
Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of)
Running only the file plugin tests, updating the version of jasmine in the assets brought the failures down from 16 to 0. Thanks for the suggestion Michal! I will see what the results are for the rest of the plugins with the updated version of jasmine tomorrow. Thanks, Edna Morales From: Michal Mocny To: dev Date: 08/27/2014 04:48 PM Subject:Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of) Sent by:mmo...@google.com One quick thing to try is to update the version of jasmine used by the harness app. 2.0 is new and its been a while since the assets were updated. -Michal On Wed, Aug 27, 2014 at 1:14 PM, Edna Y Morales wrote: > Yeah I can confirm that behavior. I was seeing it this morning when I > noticed that some specs were showing up as failing twice? > > Thanks, > Edna Morales > > [image: Inactive hide details for Martin Gonzalez ---08/27/2014 01:06:06 > PM---During testing, sometimes a callback is reached more than]Martin > Gonzalez ---08/27/2014 01:06:06 PM---During testing, sometimes a callback > is reached more than one time, this strange behavior I've faced > > From: Martin Gonzalez > To: dev@cordova.apache.org > Date: 08/27/2014 01:06 PM > Subject: Re: iOS mobile-spec failures (was: Re: [Testing] No content to > speak of) > -- > > > > During testing, sometimes a callback is reached more than one time, this > strange behavior I've faced over Windows phone with the Media tests, > creating a loop. Then Edna test it out over iOS a few weeks ago and I > recall that some of the callbacks were reached more than once, which is > unusual. > Options: Fix that behavior over iOS, and also set some routine over the > file.tests to detect that kind of behavior, fail the test and move on with > the next, this would avoid that kind of loop. > > Could you guys confirm that kind of behavior? > > > 2014-08-27 11:47 GMT-05:00 Ian Clelland : > > > Something strange is definitely going on in the file tests; in the > vicinity > > of spec.109. Custom matchers are not being added after that spec, but if > I > > remove it, then the tests simply stop at that point. > > > > > > > > On Wed, Aug 27, 2014 at 11:40 AM, Ian Clelland > > wrote: > > > > > No, it appears that something is up with Jasmine on ios -- the custom > > > matchers aren't being attached in all cases, so I am seeing errors in > the > > > console like: > > > > > > TypeError: 'undefined' is not a function (evaluating > > > 'expect(fileEntry.name).toCanonicallyMatch(fileName)') > > > > > > because .toCanonicallyMatch is not present. It's odd, because it is > > > present in previous tests, so I don't know why it would be failing > after > > a > > > certain point. > > > > > > > > > On Wed, Aug 27, 2014 at 11:03 AM, Ian Clelland > > > > wrote: > > > > > >> I'll check that out; the file changes could be related to my commits > > >> yesterday > > >> > > >> > > >> On Wed, Aug 27, 2014 at 10:58 AM, Edna Y Morales > > > >> wrote: > > >> > > >>> I'm seeing many many failing iOS tests. They are seen across file, > > >>> file-transfer, globalization, geolocation, and media with timeout and > > >>> reference errors mostly. Can anyone else verify this or is it just > me? > > >>> > > >>> Thanks, > > >>> Edna Morales > > >>> > > >>> [image: Inactive hide details for "Sergey Grebnov (Akvelon)" > > >>> ---08/27/2014 09:39:45 AM---Vladimir Kotikov and me will join this > > testing]"Sergey > > >>> Grebnov (Akvelon)" ---08/27/2014 09:39:45 AM---Vladimir Kotikov and > me > > will > > >>> join this testing party soon and help with the testing and necessary > im > > >>> > > >>> From: "Sergey Grebnov (Akvelon)" > > >>> To: "dev@cordova.apache.org" > > >>> Date: 08/27/2014 09:39 AM > > >>> Subject: RE: [Testing] No content to speak of > > >>> -- > > >>> > > >>> > > >>> > > >>> Vladimir Kotikov and me will join this testing party soon and help > with > > >>> the testing and necessary improvements(if any). Currently we see some > > >>> problem with dynamic manual tests generation (at least in Camera >
Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of)
Yeah I can confirm that behavior. I was seeing it this morning when I noticed that some specs were showing up as failing twice? Thanks, Edna Morales From: Martin Gonzalez To: dev@cordova.apache.org Date: 08/27/2014 01:06 PM Subject:Re: iOS mobile-spec failures (was: Re: [Testing] No content to speak of) During testing, sometimes a callback is reached more than one time, this strange behavior I've faced over Windows phone with the Media tests, creating a loop. Then Edna test it out over iOS a few weeks ago and I recall that some of the callbacks were reached more than once, which is unusual. Options: Fix that behavior over iOS, and also set some routine over the file.tests to detect that kind of behavior, fail the test and move on with the next, this would avoid that kind of loop. Could you guys confirm that kind of behavior? 2014-08-27 11:47 GMT-05:00 Ian Clelland : > Something strange is definitely going on in the file tests; in the vicinity > of spec.109. Custom matchers are not being added after that spec, but if I > remove it, then the tests simply stop at that point. > > > > On Wed, Aug 27, 2014 at 11:40 AM, Ian Clelland > wrote: > > > No, it appears that something is up with Jasmine on ios -- the custom > > matchers aren't being attached in all cases, so I am seeing errors in the > > console like: > > > > TypeError: 'undefined' is not a function (evaluating > > 'expect(fileEntry.name).toCanonicallyMatch(fileName)') > > > > because .toCanonicallyMatch is not present. It's odd, because it is > > present in previous tests, so I don't know why it would be failing after > a > > certain point. > > > > > > On Wed, Aug 27, 2014 at 11:03 AM, Ian Clelland > > wrote: > > > >> I'll check that out; the file changes could be related to my commits > >> yesterday > >> > >> > >> On Wed, Aug 27, 2014 at 10:58 AM, Edna Y Morales > >> wrote: > >> > >>> I'm seeing many many failing iOS tests. They are seen across file, > >>> file-transfer, globalization, geolocation, and media with timeout and > >>> reference errors mostly. Can anyone else verify this or is it just me? > >>> > >>> Thanks, > >>> Edna Morales > >>> > >>> [image: Inactive hide details for "Sergey Grebnov (Akvelon)" > >>> ---08/27/2014 09:39:45 AM---Vladimir Kotikov and me will join this > testing]"Sergey > >>> Grebnov (Akvelon)" ---08/27/2014 09:39:45 AM---Vladimir Kotikov and me > will > >>> join this testing party soon and help with the testing and necessary im > >>> > >>> From: "Sergey Grebnov (Akvelon)" > >>> To: "dev@cordova.apache.org" > >>> Date: 08/27/2014 09:39 AM > >>> Subject: RE: [Testing] No content to speak of > >>> -- > >>> > >>> > >>> > >>> Vladimir Kotikov and me will join this testing party soon and help with > >>> the testing and necessary improvements(if any). Currently we see some > >>> problem with dynamic manual tests generation (at least in Camera > tests) on > >>> Windows due to special unsafe html restrictions on this platform, > Vladimir > >>> will send details and workaround. > >>> > >>> Thx! > >>> Sergey > >>> -Original Message- > >>> From: Martin Gonzalez [mailto:martin.c.glez.g...@gmail.com > >>> ] > >>> Sent: Wednesday, August 27, 2014 5:12 PM > >>> To: dev@cordova.apache.org > >>> Subject: Re: [Testing] No content to speak of > >>> > >>> Agree, over android it looks good, however running the tests over > >>> Windows Phone, the final count is 13 new fails. > >>> Specs failing: 9, 9.5, 10, 11, 15, 24, 82, 110, 116, 121, 122, 123, > 124. > >>> > >>> > >>> > >>> 2014-08-26 11:20 GMT-05:00 Marcel Kinard : > >>> > >>> > Thanks, Ian! On Android 4.4, I'm now getting no failures with the all > >>> > the automatic tests (new-style plugin tests and old-style non-plugin > >>> tests). > >>> > > >>> > Now to start poking at the manual tests... > >>> > > >>> > On Aug 26, 2014, at 11:27 AM, Ian Clelland > >>> wrote: > >>> > > >>> > > The other issue should be resolved now, but if someone with a WP8 > >>> > > device can test it out as well, it'd be appreciated. > >>> > > >>> > > >>> > >>> > >>> -- > >>> Regards, > >>> Martin Gonzalez > >>> > >>> > >> > > > -- Regards, Martin Gonzalez
RE: [Testing] No content to speak of
I'm seeing many many failing iOS tests. They are seen across file, file-transfer, globalization, geolocation, and media with timeout and reference errors mostly. Can anyone else verify this or is it just me? Thanks, Edna Morales From: "Sergey Grebnov (Akvelon)" To: "dev@cordova.apache.org" Date: 08/27/2014 09:39 AM Subject:RE: [Testing] No content to speak of Vladimir Kotikov and me will join this testing party soon and help with the testing and necessary improvements(if any). Currently we see some problem with dynamic manual tests generation (at least in Camera tests) on Windows due to special unsafe html restrictions on this platform, Vladimir will send details and workaround. Thx! Sergey -Original Message- From: Martin Gonzalez [mailto:martin.c.glez.g...@gmail.com] Sent: Wednesday, August 27, 2014 5:12 PM To: dev@cordova.apache.org Subject: Re: [Testing] No content to speak of Agree, over android it looks good, however running the tests over Windows Phone, the final count is 13 new fails. Specs failing: 9, 9.5, 10, 11, 15, 24, 82, 110, 116, 121, 122, 123, 124. 2014-08-26 11:20 GMT-05:00 Marcel Kinard : > Thanks, Ian! On Android 4.4, I'm now getting no failures with the all > the automatic tests (new-style plugin tests and old-style non-plugin tests). > > Now to start poking at the manual tests... > > On Aug 26, 2014, at 11:27 AM, Ian Clelland wrote: > > > The other issue should be resolved now, but if someone with a WP8 > > device can test it out as well, it'd be appreciated. > > -- Regards, Martin Gonzalez
Re: [iOS 8] Please duplicate this Apple bug report for WKWebView use in Cordova
Done. Thanks, Edna Morales From: Shazron To: "dev@cordova.apache.org" Date: 08/15/2014 10:09 PM Subject:[iOS 8] Please duplicate this Apple bug report for WKWebView use in Cordova As you know the more dupes the more attention a bug gets. So if you have an Apple ID, please go to: http://bugreporter.apple.com and essentially copy my report: http://openradar.appspot.com/radar?id=5839348817723392 The test project is here (just point them to the URL): https://github.com/shazron/WKWebViewFIleUrlTest
Clarification for Camera manual tests
Hi all, I am currently working on adding some documentation to all of the manual tests (expected results, test process, etc). Looking at the camera manual tests, I see that there are several different options to test for getting a picture (source type, destination type, target width, allowEdit, correctOrientation, etc). I was hoping to get some feedback on what the original intention for these tests were. I do not think it is necessary to test every single possible combination of options, as that would be very time consuming. I think selecting a specific set of combinations to test that maximizes coverage, and documenting that for the tester to follow should be sufficient. However, I am open to any thoughts or suggestions. Thanks, Edna Morales, Developer - Apache Cordova
Introduction and JIRA help
Hi all, My name is Edna Morales and I recently joined the Cordova team at IBM so I just wanted to introduce myself. I am a recent grad from Virginia Tech and I will be focusing on iOS within the Cordova team. I am trying to assign an issue to myself, but it seems I may not have permissions or I may not be added to the list. I was hoping someone could help me out with that. Thanks, Edna Morales, Developer - Apache Cordova
