RE: Tagging 3.1.0 today?

[Steven Gill]

We did a plugins release last week. This will have to wait until the next
plugins release which could be later this week or next
On Oct 1, 2013 10:49 PM, "Maxime LUCE"  wrote:

> About File Transfer plugin :
> Will the dev branch be merged into 3.1 branch before plugins release ?
>
> I see some issues in Windows 8 proxy which are resolved in dev branch and
> not in 3.1 one.
>
> Cordialement.
>
>
> Maxime LUCE
>
>
> max...@touchit.fr
> 06 28 60 72 34
> http://touchit.fr
>
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: mercredi 2 octobre 2013 07:03
> To: dev@cordova.apache.org
> Subject: Re: Tagging 3.1.0 today?
>
> I have updated the cordova-3.1.x branches for the CLI and Plugman. I
> believe they are both ready to be published on npm.
>
> I can publish plugman but I am not listed as a maintainer for the CLI. Can
> someone either add me as a maintainer for cordova on NPM or publish it for
> me?
>
> My NPM username is stevegill.
>
> I am going to wait until tomorrow to publish plugman. Hopefully other
> people get a chance to play with them before they go live. If you do,
> remember that the CLI is looking for plugman version 0.13.0 which isn't
> published to npm yet. You will have to add the plugman folder under your
> modules to have it work.
>
> I will put together the 3.1.0 zip release tomorrow as well.
>
> -Steve
>
>
> On Tue, Oct 1, 2013 at 7:31 PM, Steven Gill 
> wrote:
>
> > Sounds good. Add it to the docs and lets make sure it makes it in the
> > 3.1.0 blog post
> >
> >
> > On Tue, Oct 1, 2013 at 7:27 PM, Ian Clelland  >wrote:
> >
> >> I thought that I had done everything for the blog review earlier, but
> >> apparently I missed the "hit the publish button" step. >:(
> >>
> >> I found one doc issue -- the whitelist docs haven't been updated for
> >> iOS and Android, and it's a potentially breaking change, so I'd like
> >> to get those updates pushed, and have at least a mention in the
> >> release notes about it.
> >>
> >> I'm raking the docs right now and I'll retag if necessary.
> >>
> >>
> >> On Tue, Oct 1, 2013 at 9:27 PM, Jesse  wrote:
> >>
> >> > Here is a brief summary for wp7 + wp8 and windows8
> >> >
> >> >
> >> > Windows Phone 7 + 8 Platform updates ===
> >> >
> >> > Defects closed:
> >> >
> >> > CB-3177 remove  support in config.xml and remove
> >> > deprecation
> >> notice
> >> > in WP8
> >> > CB-3176 remove  support in config.xml and remove
> >> > deprecation
> >> notice
> >> > in WP7
> >> > CB-4385 Tooling scripts fail when there are spaces in the path name
> >> > CB-4350 bad errors when trying to add win* platforms on mac
> >> > CB-4421 WP8 Project - XHRHelper.HandleCommand failing with
> >> > 'System.InvalidOperationException
> >> > CB-4807 WP7 + 8 cannot handle parsing config.xml with namespaces
> >> > CB-4526 Windows Phone 7+8 `build` script with no flags should call
> >> `clean`
> >> > first
> >> > CB-4850 Apache Cordova Apache CordovaCB-4850 WP7 startup
> >> > optimization
> >> >
> >> > platform script improvements, removed case-sensitive ms-build
> >> > version checks affecting some international users.
> >> > added hash removal to injected js for backbone + jQuery Mobile
> >> > routes
> >> >
> >> >
> >> >
> >> > Windows 8 Platform updates
> >> > ===
> >> >
> >> > Windows 8 support has been added to cordova-cli, so you can call :
> >> cordova
> >> > platform add windows8 on your cordova-cli projects
> >> >
> >> > all plugins were broken out into the respective repos all plugins
> >> > are fully supported to be installed/uninstalled with
> >> plugman,
> >> > and cordova-cli
> >> >
> >> > supported plugins include :
> >> > org.apache.cordova.camera
> >> > org.apache.cordova.console
> >> > org.apache.cordova.device.motion
> >> > org.apache.cordova.device.orientation
> >> > org.apache.cordova.device
> >> > org.apache.cordova.dialogs
> >> > org.apache.cordova.file-transfer
> >> > org.apache.cordova.file
> >> > org.apache.cordova.geolocation
> >> > org.apache.cordova.inappbrowser ( some limitations because of
> >> > iframe use and security model ) org.apache.cordova.media-capture
> >> > org.apache.cordova.network-information
> >> >
> >> >
> >> > @purplecabbage
> >> > risingj.com
> >> >
> >> >
> >> > On Tue, Oct 1, 2013 at 6:10 PM, Steven Gill
> >> > 
> >> > wrote:
> >> >
> >> > > Looks like Jeff already pushed it. I am updating cordova-3.1.x
> >> > > right
> >> now
> >> > >
> >> > >
> >> > > On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve
> >> > > 
> >> > > wrote:
> >> > >
> >> > > > Jeff - is there a JIRA issue for the bug? Would be good to mark
> >> > > > it
> >> as a
> >> > > > dependent of https://issues.apache.org/jira/browse/CB-4843.
> >> > > >
> >> > > > Bryan - thanks for the write-up! I've updated the review
> >> > > > request
> >> with
> >> > > your
> >> > > > blurb.
> >> > > >
> >> > > > Steven - CadVer-SemVer sounds good.
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill <
> >> stevengil...@gm

RE: Tagging 3.1.0 today?

[Maxime LUCE]

About File Transfer plugin :
Will the dev branch be merged into 3.1 branch before plugins release ?

I see some issues in Windows 8 proxy which are resolved in dev branch and not 
in 3.1 one.

Cordialement.


Maxime LUCE


max...@touchit.fr
06 28 60 72 34
http://touchit.fr


-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: mercredi 2 octobre 2013 07:03
To: dev@cordova.apache.org
Subject: Re: Tagging 3.1.0 today?

I have updated the cordova-3.1.x branches for the CLI and Plugman. I believe 
they are both ready to be published on npm.

I can publish plugman but I am not listed as a maintainer for the CLI. Can 
someone either add me as a maintainer for cordova on NPM or publish it for me?

My NPM username is stevegill.

I am going to wait until tomorrow to publish plugman. Hopefully other people 
get a chance to play with them before they go live. If you do, remember that 
the CLI is looking for plugman version 0.13.0 which isn't published to npm yet. 
You will have to add the plugman folder under your modules to have it work.

I will put together the 3.1.0 zip release tomorrow as well.

-Steve


On Tue, Oct 1, 2013 at 7:31 PM, Steven Gill  wrote:

> Sounds good. Add it to the docs and lets make sure it makes it in the
> 3.1.0 blog post
>
>
> On Tue, Oct 1, 2013 at 7:27 PM, Ian Clelland wrote:
>
>> I thought that I had done everything for the blog review earlier, but 
>> apparently I missed the "hit the publish button" step. >:(
>>
>> I found one doc issue -- the whitelist docs haven't been updated for 
>> iOS and Android, and it's a potentially breaking change, so I'd like 
>> to get those updates pushed, and have at least a mention in the 
>> release notes about it.
>>
>> I'm raking the docs right now and I'll retag if necessary.
>>
>>
>> On Tue, Oct 1, 2013 at 9:27 PM, Jesse  wrote:
>>
>> > Here is a brief summary for wp7 + wp8 and windows8
>> >
>> >
>> > Windows Phone 7 + 8 Platform updates ===
>> >
>> > Defects closed:
>> >
>> > CB-3177 remove  support in config.xml and remove 
>> > deprecation
>> notice
>> > in WP8
>> > CB-3176 remove  support in config.xml and remove 
>> > deprecation
>> notice
>> > in WP7
>> > CB-4385 Tooling scripts fail when there are spaces in the path name
>> > CB-4350 bad errors when trying to add win* platforms on mac
>> > CB-4421 WP8 Project - XHRHelper.HandleCommand failing with 
>> > 'System.InvalidOperationException
>> > CB-4807 WP7 + 8 cannot handle parsing config.xml with namespaces
>> > CB-4526 Windows Phone 7+8 `build` script with no flags should call
>> `clean`
>> > first
>> > CB-4850 Apache Cordova Apache CordovaCB-4850 WP7 startup 
>> > optimization
>> >
>> > platform script improvements, removed case-sensitive ms-build 
>> > version checks affecting some international users.
>> > added hash removal to injected js for backbone + jQuery Mobile 
>> > routes
>> >
>> >
>> >
>> > Windows 8 Platform updates
>> > ===
>> >
>> > Windows 8 support has been added to cordova-cli, so you can call :
>> cordova
>> > platform add windows8 on your cordova-cli projects
>> >
>> > all plugins were broken out into the respective repos all plugins 
>> > are fully supported to be installed/uninstalled with
>> plugman,
>> > and cordova-cli
>> >
>> > supported plugins include :
>> > org.apache.cordova.camera
>> > org.apache.cordova.console
>> > org.apache.cordova.device.motion
>> > org.apache.cordova.device.orientation
>> > org.apache.cordova.device
>> > org.apache.cordova.dialogs
>> > org.apache.cordova.file-transfer
>> > org.apache.cordova.file
>> > org.apache.cordova.geolocation
>> > org.apache.cordova.inappbrowser ( some limitations because of 
>> > iframe use and security model ) org.apache.cordova.media-capture 
>> > org.apache.cordova.network-information
>> >
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Tue, Oct 1, 2013 at 6:10 PM, Steven Gill 
>> > 
>> > wrote:
>> >
>> > > Looks like Jeff already pushed it. I am updating cordova-3.1.x 
>> > > right
>> now
>> > >
>> > >
>> > > On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve 
>> > > 
>> > > wrote:
>> > >
>> > > > Jeff - is there a JIRA issue for the bug? Would be good to mark 
>> > > > it
>> as a
>> > > > dependent of https://issues.apache.org/jira/browse/CB-4843.
>> > > >
>> > > > Bryan - thanks for the write-up! I've updated the review 
>> > > > request
>> with
>> > > your
>> > > > blurb.
>> > > >
>> > > > Steven - CadVer-SemVer sounds good.
>> > > >
>> > > >
>> > > >
>> > > > On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill <
>> stevengil...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > According to
>> > > http://wiki.apache.org/cordova/VersioningAndReleaseStrategy
>> > > > ,
>> > > > > it looks like we were leaning towards CadVer-SemVer for the 
>> > > > > CLI. I
>> > just
>> > > > > think it would be weird to only make it CadVer for this 
>> > > > > release
>> and
>> > > then
>> > > > > add on the SemVer part whenever we make little fixes for the
>> weekly
>> > > > > release.
>> > > > >

Re: Review Request 14429: 3.1 release blog post

[Steven Gill]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14429/#review26594
---


Firefox OS Platform updates
===

Firefox OS support has been added to cordova-cli, so you can call:
cordova platform add firefoxos on your cordova-cli projects.

Firefox OS support is still in the very early phases of development. We will 
continue to work towards adding support for all of cordova's APIs. Currently, 
Firefox OS support exists for two plugins. 

supported plugins include:
org.apache.cordova.vibration
org.apache.cordova.device

- Steven Gill


On Oct. 2, 2013, 12:47 a.m., Andrew Grieve wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14429/
> ---
> 
> (Updated Oct. 2, 2013, 12:47 a.m.)
> 
> 
> Review request for cordova.
> 
> 
> Repository: cordova-site
> 
> 
> Description
> ---
> 
> 3.1 release blog post
> 
> 
> Diffs
> -
> 
>   /cordova/site/www/_posts/2013-10-01-cordova-31.md PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/14429/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andrew Grieve
> 
>

Re: Tagging 3.1.0 today?

[Steven Gill]

I have updated the cordova-3.1.x branches for the CLI and Plugman. I
believe they are both ready to be published on npm.

I can publish plugman but I am not listed as a maintainer for the CLI. Can
someone either add me as a maintainer for cordova on NPM or publish it for
me?

My NPM username is stevegill.

I am going to wait until tomorrow to publish plugman. Hopefully other
people get a chance to play with them before they go live. If you do,
remember that the CLI is looking for plugman version 0.13.0 which isn't
published to npm yet. You will have to add the plugman folder under your
modules to have it work.

I will put together the 3.1.0 zip release tomorrow as well.

-Steve


On Tue, Oct 1, 2013 at 7:31 PM, Steven Gill  wrote:

> Sounds good. Add it to the docs and lets make sure it makes it in the
> 3.1.0 blog post
>
>
> On Tue, Oct 1, 2013 at 7:27 PM, Ian Clelland wrote:
>
>> I thought that I had done everything for the blog review earlier, but
>> apparently I missed the "hit the publish button" step. >:(
>>
>> I found one doc issue -- the whitelist docs haven't been updated for iOS
>> and Android, and it's a potentially breaking change, so I'd like to get
>> those updates pushed, and have at least a mention in the release notes
>> about it.
>>
>> I'm raking the docs right now and I'll retag if necessary.
>>
>>
>> On Tue, Oct 1, 2013 at 9:27 PM, Jesse  wrote:
>>
>> > Here is a brief summary for wp7 + wp8 and windows8
>> >
>> >
>> > Windows Phone 7 + 8 Platform updates
>> > ===
>> >
>> > Defects closed:
>> >
>> > CB-3177 remove  support in config.xml and remove deprecation
>> notice
>> > in WP8
>> > CB-3176 remove  support in config.xml and remove deprecation
>> notice
>> > in WP7
>> > CB-4385 Tooling scripts fail when there are spaces in the path name
>> > CB-4350 bad errors when trying to add win* platforms on mac
>> > CB-4421 WP8 Project - XHRHelper.HandleCommand failing with
>> > 'System.InvalidOperationException
>> > CB-4807 WP7 + 8 cannot handle parsing config.xml with namespaces
>> > CB-4526 Windows Phone 7+8 `build` script with no flags should call
>> `clean`
>> > first
>> > CB-4850 Apache Cordova Apache CordovaCB-4850 WP7 startup optimization
>> >
>> > platform script improvements, removed case-sensitive ms-build version
>> > checks affecting some international users.
>> > added hash removal to injected js for backbone + jQuery Mobile routes
>> >
>> >
>> >
>> > Windows 8 Platform updates
>> > ===
>> >
>> > Windows 8 support has been added to cordova-cli, so you can call :
>> cordova
>> > platform add windows8 on your cordova-cli projects
>> >
>> > all plugins were broken out into the respective repos
>> > all plugins are fully supported to be installed/uninstalled with
>> plugman,
>> > and cordova-cli
>> >
>> > supported plugins include :
>> > org.apache.cordova.camera
>> > org.apache.cordova.console
>> > org.apache.cordova.device.motion
>> > org.apache.cordova.device.orientation
>> > org.apache.cordova.device
>> > org.apache.cordova.dialogs
>> > org.apache.cordova.file-transfer
>> > org.apache.cordova.file
>> > org.apache.cordova.geolocation
>> > org.apache.cordova.inappbrowser ( some limitations because of iframe use
>> > and security model )
>> > org.apache.cordova.media-capture
>> > org.apache.cordova.network-information
>> >
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Tue, Oct 1, 2013 at 6:10 PM, Steven Gill 
>> > wrote:
>> >
>> > > Looks like Jeff already pushed it. I am updating cordova-3.1.x right
>> now
>> > >
>> > >
>> > > On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve 
>> > > wrote:
>> > >
>> > > > Jeff - is there a JIRA issue for the bug? Would be good to mark it
>> as a
>> > > > dependent of https://issues.apache.org/jira/browse/CB-4843.
>> > > >
>> > > > Bryan - thanks for the write-up! I've updated the review request
>> with
>> > > your
>> > > > blurb.
>> > > >
>> > > > Steven - CadVer-SemVer sounds good.
>> > > >
>> > > >
>> > > >
>> > > > On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill <
>> stevengil...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > According to
>> > > http://wiki.apache.org/cordova/VersioningAndReleaseStrategy
>> > > > ,
>> > > > > it looks like we were leaning towards CadVer-SemVer for the CLI. I
>> > just
>> > > > > think it would be weird to only make it CadVer for this release
>> and
>> > > then
>> > > > > add on the SemVer part whenever we make little fixes for the
>> weekly
>> > > > > release.
>> > > > >
>> > > > >
>> > > > > On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve <
>> agri...@chromium.org>
>> > > > > wrote:
>> > > > >
>> > > > > > On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill <
>> > stevengil...@gmail.com
>> > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > FFOS is tagged.
>> > > > > > >
>> > > > > > > Looks like windows platforms and blackberry have been tagged
>> as
>> > > > well. I
>> > > > > > saw
>> > > > > > > the tags on the repos and went ahead and closed the issues.
>> Let
>> > me
>> > > > know
>> > > > > > if
>> > > > >

Re: Tagging 3.1.0 today?

[Steven Gill]

Sounds good. Add it to the docs and lets make sure it makes it in the 3.1.0
blog post


On Tue, Oct 1, 2013 at 7:27 PM, Ian Clelland  wrote:

> I thought that I had done everything for the blog review earlier, but
> apparently I missed the "hit the publish button" step. >:(
>
> I found one doc issue -- the whitelist docs haven't been updated for iOS
> and Android, and it's a potentially breaking change, so I'd like to get
> those updates pushed, and have at least a mention in the release notes
> about it.
>
> I'm raking the docs right now and I'll retag if necessary.
>
>
> On Tue, Oct 1, 2013 at 9:27 PM, Jesse  wrote:
>
> > Here is a brief summary for wp7 + wp8 and windows8
> >
> >
> > Windows Phone 7 + 8 Platform updates
> > ===
> >
> > Defects closed:
> >
> > CB-3177 remove  support in config.xml and remove deprecation
> notice
> > in WP8
> > CB-3176 remove  support in config.xml and remove deprecation
> notice
> > in WP7
> > CB-4385 Tooling scripts fail when there are spaces in the path name
> > CB-4350 bad errors when trying to add win* platforms on mac
> > CB-4421 WP8 Project - XHRHelper.HandleCommand failing with
> > 'System.InvalidOperationException
> > CB-4807 WP7 + 8 cannot handle parsing config.xml with namespaces
> > CB-4526 Windows Phone 7+8 `build` script with no flags should call
> `clean`
> > first
> > CB-4850 Apache Cordova Apache CordovaCB-4850 WP7 startup optimization
> >
> > platform script improvements, removed case-sensitive ms-build version
> > checks affecting some international users.
> > added hash removal to injected js for backbone + jQuery Mobile routes
> >
> >
> >
> > Windows 8 Platform updates
> > ===
> >
> > Windows 8 support has been added to cordova-cli, so you can call :
> cordova
> > platform add windows8 on your cordova-cli projects
> >
> > all plugins were broken out into the respective repos
> > all plugins are fully supported to be installed/uninstalled with plugman,
> > and cordova-cli
> >
> > supported plugins include :
> > org.apache.cordova.camera
> > org.apache.cordova.console
> > org.apache.cordova.device.motion
> > org.apache.cordova.device.orientation
> > org.apache.cordova.device
> > org.apache.cordova.dialogs
> > org.apache.cordova.file-transfer
> > org.apache.cordova.file
> > org.apache.cordova.geolocation
> > org.apache.cordova.inappbrowser ( some limitations because of iframe use
> > and security model )
> > org.apache.cordova.media-capture
> > org.apache.cordova.network-information
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Oct 1, 2013 at 6:10 PM, Steven Gill 
> > wrote:
> >
> > > Looks like Jeff already pushed it. I am updating cordova-3.1.x right
> now
> > >
> > >
> > > On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve 
> > > wrote:
> > >
> > > > Jeff - is there a JIRA issue for the bug? Would be good to mark it
> as a
> > > > dependent of https://issues.apache.org/jira/browse/CB-4843.
> > > >
> > > > Bryan - thanks for the write-up! I've updated the review request with
> > > your
> > > > blurb.
> > > >
> > > > Steven - CadVer-SemVer sounds good.
> > > >
> > > >
> > > >
> > > > On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill  >
> > > > wrote:
> > > >
> > > > > According to
> > > http://wiki.apache.org/cordova/VersioningAndReleaseStrategy
> > > > ,
> > > > > it looks like we were leaning towards CadVer-SemVer for the CLI. I
> > just
> > > > > think it would be weird to only make it CadVer for this release and
> > > then
> > > > > add on the SemVer part whenever we make little fixes for the weekly
> > > > > release.
> > > > >
> > > > >
> > > > > On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve <
> agri...@chromium.org>
> > > > > wrote:
> > > > >
> > > > > > On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill <
> > stevengil...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > FFOS is tagged.
> > > > > > >
> > > > > > > Looks like windows platforms and blackberry have been tagged as
> > > > well. I
> > > > > > saw
> > > > > > > the tags on the repos and went ahead and closed the issues. Let
> > me
> > > > know
> > > > > > if
> > > > > > > you guys didn't want those issues closed just yet.
> > > > > > >
> > > > > > > Only things remaining are retagging docs, tagging cli, tagging
> > > > plugman,
> > > > > > > uploading the release and posting the blog post.
> > > > > > >
> > > > > > > I merged in Jesse's windows 8 pull requests to cordova-3.1.x
> > > branches
> > > > > of
> > > > > > > the CLI + Plugman locally on my machine. I am running into some
> > > > errors
> > > > > > when
> > > > > > > adding windows8 as a platform. I will chat with Jesse and once
> > that
> > > > is
> > > > > > > sorted, I will push the updates up to apache.
> > > > > > >
> > > > > > > With CLI and Plugman, do we want to increase the version from
> the
> > > RC?
> > > > > The
> > > > > > > RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it
> would
> > > make
> > > > > the
> > > > > > > most sense to update those to 3.0.11 and 0.13.0 instead of
> > > retaggi

Re: Tagging 3.1.0 today?

[Ian Clelland]

I thought that I had done everything for the blog review earlier, but
apparently I missed the "hit the publish button" step. >:(

I found one doc issue -- the whitelist docs haven't been updated for iOS
and Android, and it's a potentially breaking change, so I'd like to get
those updates pushed, and have at least a mention in the release notes
about it.

I'm raking the docs right now and I'll retag if necessary.


On Tue, Oct 1, 2013 at 9:27 PM, Jesse  wrote:

> Here is a brief summary for wp7 + wp8 and windows8
>
>
> Windows Phone 7 + 8 Platform updates
> ===
>
> Defects closed:
>
> CB-3177 remove  support in config.xml and remove deprecation notice
> in WP8
> CB-3176 remove  support in config.xml and remove deprecation notice
> in WP7
> CB-4385 Tooling scripts fail when there are spaces in the path name
> CB-4350 bad errors when trying to add win* platforms on mac
> CB-4421 WP8 Project - XHRHelper.HandleCommand failing with
> 'System.InvalidOperationException
> CB-4807 WP7 + 8 cannot handle parsing config.xml with namespaces
> CB-4526 Windows Phone 7+8 `build` script with no flags should call `clean`
> first
> CB-4850 Apache Cordova Apache CordovaCB-4850 WP7 startup optimization
>
> platform script improvements, removed case-sensitive ms-build version
> checks affecting some international users.
> added hash removal to injected js for backbone + jQuery Mobile routes
>
>
>
> Windows 8 Platform updates
> ===
>
> Windows 8 support has been added to cordova-cli, so you can call : cordova
> platform add windows8 on your cordova-cli projects
>
> all plugins were broken out into the respective repos
> all plugins are fully supported to be installed/uninstalled with plugman,
> and cordova-cli
>
> supported plugins include :
> org.apache.cordova.camera
> org.apache.cordova.console
> org.apache.cordova.device.motion
> org.apache.cordova.device.orientation
> org.apache.cordova.device
> org.apache.cordova.dialogs
> org.apache.cordova.file-transfer
> org.apache.cordova.file
> org.apache.cordova.geolocation
> org.apache.cordova.inappbrowser ( some limitations because of iframe use
> and security model )
> org.apache.cordova.media-capture
> org.apache.cordova.network-information
>
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Oct 1, 2013 at 6:10 PM, Steven Gill 
> wrote:
>
> > Looks like Jeff already pushed it. I am updating cordova-3.1.x right now
> >
> >
> > On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve 
> > wrote:
> >
> > > Jeff - is there a JIRA issue for the bug? Would be good to mark it as a
> > > dependent of https://issues.apache.org/jira/browse/CB-4843.
> > >
> > > Bryan - thanks for the write-up! I've updated the review request with
> > your
> > > blurb.
> > >
> > > Steven - CadVer-SemVer sounds good.
> > >
> > >
> > >
> > > On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill 
> > > wrote:
> > >
> > > > According to
> > http://wiki.apache.org/cordova/VersioningAndReleaseStrategy
> > > ,
> > > > it looks like we were leaning towards CadVer-SemVer for the CLI. I
> just
> > > > think it would be weird to only make it CadVer for this release and
> > then
> > > > add on the SemVer part whenever we make little fixes for the weekly
> > > > release.
> > > >
> > > >
> > > > On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve 
> > > > wrote:
> > > >
> > > > > On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill <
> stevengil...@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > FFOS is tagged.
> > > > > >
> > > > > > Looks like windows platforms and blackberry have been tagged as
> > > well. I
> > > > > saw
> > > > > > the tags on the repos and went ahead and closed the issues. Let
> me
> > > know
> > > > > if
> > > > > > you guys didn't want those issues closed just yet.
> > > > > >
> > > > > > Only things remaining are retagging docs, tagging cli, tagging
> > > plugman,
> > > > > > uploading the release and posting the blog post.
> > > > > >
> > > > > > I merged in Jesse's windows 8 pull requests to cordova-3.1.x
> > branches
> > > > of
> > > > > > the CLI + Plugman locally on my machine. I am running into some
> > > errors
> > > > > when
> > > > > > adding windows8 as a platform. I will chat with Jesse and once
> that
> > > is
> > > > > > sorted, I will push the updates up to apache.
> > > > > >
> > > > > > With CLI and Plugman, do we want to increase the version from the
> > RC?
> > > > The
> > > > > > RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would
> > make
> > > > the
> > > > > > most sense to update those to 3.0.11 and 0.13.0 instead of
> > retagging
> > > > > those
> > > > > > on npm. Thoughts?
> > > > > >
> > > > >
> > > > > Updating version makes sense to me. There is still some debate over
> > > what
> > > > > the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0")
> > I'd
> > > > > like the former
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Oct 1, 2013 at 2:10 PM, Shazron 
> wrote:
> > > > > >
> > > > > > > Do you mind doing it

Re: Review Request 14429: 3.1 release blog post

[Ian Clelland]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14429/#review26578
---



/cordova/site/www/_posts/2013-10-01-cordova-31.md


This is actually a potentially breaking change for developers -- I had 
forgotten that this didn't make it into 3.0, and this is the first time that 
developers are going to encounter it.

The documentation does not appear to be up-to-date; I will fix that tonight.

Should there be a note in the blog, or the release notes at least, that 
devs might have to change their access rules?


- Ian Clelland


On Oct. 2, 2013, 12:47 a.m., Andrew Grieve wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14429/
> ---
> 
> (Updated Oct. 2, 2013, 12:47 a.m.)
> 
> 
> Review request for cordova.
> 
> 
> Repository: cordova-site
> 
> 
> Description
> ---
> 
> 3.1 release blog post
> 
> 
> Diffs
> -
> 
>   /cordova/site/www/_posts/2013-10-01-cordova-31.md PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/14429/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andrew Grieve
> 
>

Re: Tagging 3.1.0 today?

[Jesse]

Here is a brief summary for wp7 + wp8 and windows8


Windows Phone 7 + 8 Platform updates
===

Defects closed:

CB-3177 remove  support in config.xml and remove deprecation notice
in WP8
CB-3176 remove  support in config.xml and remove deprecation notice
in WP7
CB-4385 Tooling scripts fail when there are spaces in the path name
CB-4350 bad errors when trying to add win* platforms on mac
CB-4421 WP8 Project - XHRHelper.HandleCommand failing with
'System.InvalidOperationException
CB-4807 WP7 + 8 cannot handle parsing config.xml with namespaces
CB-4526 Windows Phone 7+8 `build` script with no flags should call `clean`
first
CB-4850 Apache Cordova Apache CordovaCB-4850 WP7 startup optimization

platform script improvements, removed case-sensitive ms-build version
checks affecting some international users.
added hash removal to injected js for backbone + jQuery Mobile routes



Windows 8 Platform updates
===

Windows 8 support has been added to cordova-cli, so you can call : cordova
platform add windows8 on your cordova-cli projects

all plugins were broken out into the respective repos
all plugins are fully supported to be installed/uninstalled with plugman,
and cordova-cli

supported plugins include :
org.apache.cordova.camera
org.apache.cordova.console
org.apache.cordova.device.motion
org.apache.cordova.device.orientation
org.apache.cordova.device
org.apache.cordova.dialogs
org.apache.cordova.file-transfer
org.apache.cordova.file
org.apache.cordova.geolocation
org.apache.cordova.inappbrowser ( some limitations because of iframe use
and security model )
org.apache.cordova.media-capture
org.apache.cordova.network-information


@purplecabbage
risingj.com


On Tue, Oct 1, 2013 at 6:10 PM, Steven Gill  wrote:

> Looks like Jeff already pushed it. I am updating cordova-3.1.x right now
>
>
> On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve 
> wrote:
>
> > Jeff - is there a JIRA issue for the bug? Would be good to mark it as a
> > dependent of https://issues.apache.org/jira/browse/CB-4843.
> >
> > Bryan - thanks for the write-up! I've updated the review request with
> your
> > blurb.
> >
> > Steven - CadVer-SemVer sounds good.
> >
> >
> >
> > On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill 
> > wrote:
> >
> > > According to
> http://wiki.apache.org/cordova/VersioningAndReleaseStrategy
> > ,
> > > it looks like we were leaning towards CadVer-SemVer for the CLI. I just
> > > think it would be weird to only make it CadVer for this release and
> then
> > > add on the SemVer part whenever we make little fixes for the weekly
> > > release.
> > >
> > >
> > > On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve 
> > > wrote:
> > >
> > > > On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill  >
> > > > wrote:
> > > >
> > > > > FFOS is tagged.
> > > > >
> > > > > Looks like windows platforms and blackberry have been tagged as
> > well. I
> > > > saw
> > > > > the tags on the repos and went ahead and closed the issues. Let me
> > know
> > > > if
> > > > > you guys didn't want those issues closed just yet.
> > > > >
> > > > > Only things remaining are retagging docs, tagging cli, tagging
> > plugman,
> > > > > uploading the release and posting the blog post.
> > > > >
> > > > > I merged in Jesse's windows 8 pull requests to cordova-3.1.x
> branches
> > > of
> > > > > the CLI + Plugman locally on my machine. I am running into some
> > errors
> > > > when
> > > > > adding windows8 as a platform. I will chat with Jesse and once that
> > is
> > > > > sorted, I will push the updates up to apache.
> > > > >
> > > > > With CLI and Plugman, do we want to increase the version from the
> RC?
> > > The
> > > > > RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would
> make
> > > the
> > > > > most sense to update those to 3.0.11 and 0.13.0 instead of
> retagging
> > > > those
> > > > > on npm. Thoughts?
> > > > >
> > > >
> > > > Updating version makes sense to me. There is still some debate over
> > what
> > > > the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0")
> I'd
> > > > like the former
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:
> > > > >
> > > > > > Do you mind doing it? I think we've always deleted and re-tagged
> > > using
> > > > > the
> > > > > > same name
> > > > > >
> > > > > >
> > > > > > On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard <
> cmarc...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Shaz, do you want to take care of that, or would you like me
> to?
> > > > > > >
> > > > > > > When doing a re-tag, do we do the sane thing (use a modified
> tag
> > > > name)
> > > > > or
> > > > > > > the insane thing (reuse the same tag name)?
> > > > > > >
> > > > > > > Looks like you already put the change in both the en/edge and
> > > > en/3.1.0
> > > > > > > dirs. Nice.
> > > > > > >
> > > > > > > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> > > > > > >
> > > > > > > > Added
> > > > > > >
> > > >
> http://git-wip-us.apache.org/

Re: Tagging 3.1.0 today?

[Steven Gill]

Looks like Jeff already pushed it. I am updating cordova-3.1.x right now


On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve  wrote:

> Jeff - is there a JIRA issue for the bug? Would be good to mark it as a
> dependent of https://issues.apache.org/jira/browse/CB-4843.
>
> Bryan - thanks for the write-up! I've updated the review request with your
> blurb.
>
> Steven - CadVer-SemVer sounds good.
>
>
>
> On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill 
> wrote:
>
> > According to http://wiki.apache.org/cordova/VersioningAndReleaseStrategy
> ,
> > it looks like we were leaning towards CadVer-SemVer for the CLI. I just
> > think it would be weird to only make it CadVer for this release and then
> > add on the SemVer part whenever we make little fixes for the weekly
> > release.
> >
> >
> > On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve 
> > wrote:
> >
> > > On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill 
> > > wrote:
> > >
> > > > FFOS is tagged.
> > > >
> > > > Looks like windows platforms and blackberry have been tagged as
> well. I
> > > saw
> > > > the tags on the repos and went ahead and closed the issues. Let me
> know
> > > if
> > > > you guys didn't want those issues closed just yet.
> > > >
> > > > Only things remaining are retagging docs, tagging cli, tagging
> plugman,
> > > > uploading the release and posting the blog post.
> > > >
> > > > I merged in Jesse's windows 8 pull requests to cordova-3.1.x branches
> > of
> > > > the CLI + Plugman locally on my machine. I am running into some
> errors
> > > when
> > > > adding windows8 as a platform. I will chat with Jesse and once that
> is
> > > > sorted, I will push the updates up to apache.
> > > >
> > > > With CLI and Plugman, do we want to increase the version from the RC?
> > The
> > > > RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would make
> > the
> > > > most sense to update those to 3.0.11 and 0.13.0 instead of retagging
> > > those
> > > > on npm. Thoughts?
> > > >
> > >
> > > Updating version makes sense to me. There is still some debate over
> what
> > > the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0") I'd
> > > like the former
> > >
> > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:
> > > >
> > > > > Do you mind doing it? I think we've always deleted and re-tagged
> > using
> > > > the
> > > > > same name
> > > > >
> > > > >
> > > > > On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard 
> > > > wrote:
> > > > >
> > > > > > Shaz, do you want to take care of that, or would you like me to?
> > > > > >
> > > > > > When doing a re-tag, do we do the sane thing (use a modified tag
> > > name)
> > > > or
> > > > > > the insane thing (reuse the same tag name)?
> > > > > >
> > > > > > Looks like you already put the change in both the en/edge and
> > > en/3.1.0
> > > > > > dirs. Nice.
> > > > > >
> > > > > > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> > > > > >
> > > > > > > Added
> > > > > >
> > > http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > > > > > > cordova-docs, needs a 3.1.0 re-tag.
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Jeff - is there a JIRA issue for the bug? Would be good to mark it as a
dependent of https://issues.apache.org/jira/browse/CB-4843.

Bryan - thanks for the write-up! I've updated the review request with your
blurb.

Steven - CadVer-SemVer sounds good.



On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill  wrote:

> According to http://wiki.apache.org/cordova/VersioningAndReleaseStrategy,
> it looks like we were leaning towards CadVer-SemVer for the CLI. I just
> think it would be weird to only make it CadVer for this release and then
> add on the SemVer part whenever we make little fixes for the weekly
> release.
>
>
> On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve 
> wrote:
>
> > On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill 
> > wrote:
> >
> > > FFOS is tagged.
> > >
> > > Looks like windows platforms and blackberry have been tagged as well. I
> > saw
> > > the tags on the repos and went ahead and closed the issues. Let me know
> > if
> > > you guys didn't want those issues closed just yet.
> > >
> > > Only things remaining are retagging docs, tagging cli, tagging plugman,
> > > uploading the release and posting the blog post.
> > >
> > > I merged in Jesse's windows 8 pull requests to cordova-3.1.x branches
> of
> > > the CLI + Plugman locally on my machine. I am running into some errors
> > when
> > > adding windows8 as a platform. I will chat with Jesse and once that is
> > > sorted, I will push the updates up to apache.
> > >
> > > With CLI and Plugman, do we want to increase the version from the RC?
> The
> > > RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would make
> the
> > > most sense to update those to 3.0.11 and 0.13.0 instead of retagging
> > those
> > > on npm. Thoughts?
> > >
> >
> > Updating version makes sense to me. There is still some debate over what
> > the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0") I'd
> > like the former
> >
> >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:
> > >
> > > > Do you mind doing it? I think we've always deleted and re-tagged
> using
> > > the
> > > > same name
> > > >
> > > >
> > > > On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard 
> > > wrote:
> > > >
> > > > > Shaz, do you want to take care of that, or would you like me to?
> > > > >
> > > > > When doing a re-tag, do we do the sane thing (use a modified tag
> > name)
> > > or
> > > > > the insane thing (reuse the same tag name)?
> > > > >
> > > > > Looks like you already put the change in both the en/edge and
> > en/3.1.0
> > > > > dirs. Nice.
> > > > >
> > > > > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> > > > >
> > > > > > Added
> > > > >
> > http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > > > > > cordova-docs, needs a 3.1.0 re-tag.
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Review Request 14429: 3.1 release blog post

[Andrew Grieve]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14429/
---

(Updated Oct. 2, 2013, 12:47 a.m.)


Review request for cordova.


Repository: cordova-site


Description
---

3.1 release blog post


Diffs (updated)
-

  /cordova/site/www/_posts/2013-10-01-cordova-31.md PRE-CREATION 

Diff: https://reviews.apache.org/r/14429/diff/


Testing
---


Thanks,

Andrew Grieve

Re: Mapping plugin ID -> URL

[Andrew Grieve]

E.g. for mobile-spec's dependency-plugin, it has  Instead of having plugman download it from
the registry, I'd like to tell it to look for it locally.

Not entirely sure what you mean by project level deps (do those exist)?


On Wed, Oct 2, 2013 at 12:45 AM, Brian LeRoux  wrote:

> So wait, the use case is proj level deps not plugin level?
> On Oct 1, 2013 10:50 PM, "Andrew Grieve"  wrote:
>
> > There is a need to have plugman look in places other than the registry
> when
> > fetching plugins by ID. This is particularly the case because
> 
> > plugins now have IDs only instead of specifying a URL.
> >
> > Downstream distributions need this (e.g. IBM packages plugins with their
> > distro). But this would be nice for mobile-spec as well (dependency
> plugin
> > could just list IDs instead of plugin paths).
> >
> > Idea #1:
> > Add a map to a project's .cordova/config.json with explicit ID -> URL
> > mappings. E.g.:
> > "plugin_map": {
> >   "org.apache.cordova.file": "file:///some/path",
> >   "org.apache.cordova.file-transfer": "http://git.com/url#hash";
> > }
> >
> > Idea #2
> > Add the idea of "plugin search path"
> > e.g.:
> > .cordova/config.json
> >"plugin_search_path": ["file:///my/local/plugins", "
> > http://my/custom/couch/db";, ""]
> >
> > Entries here can be:
> >   1. local directory where each subdirectory contains a plugin
> >   2. http:// to a couchdb of a custom registry
> >   3. , which means prepend this list instead of replacing the
> > setting.
> >
> >
> > Idea #3
> > Allow the user to copy / symlink the plugin sources into a projects
> > plugins/ directory. The directory names in here would need to be the
> plugin
> > IDs. When a request to install a plugin is made, plugman will first check
> > if it already exists within plugins/, and if so, uses that source. It
> would
> > also need to know not to delete the directory on plugin rm.
> >
> >
> >
> > #1 is nice because it's simple, but may not be super convenient (since
> you
> > need to explicitly add each plugin). It's also the only suggestion that
> > allows you to map an ID to a custom git URL
> > #2 will work well for plugin collections, but may be annoying if you just
> > want to override a single plugin location.
> > #3 is arguably the most flexible since it leaves the fetching completely
> up
> > to the user. It may encourage people to muck with their plugins/ to the
> > point of breaking their project though. (e.g. they may delete plugins
> that
> > are installed)
> >
> >
> > I think I'd lean towards allowing both #1 and #2.
> >
>

Re: Mapping plugin ID -> URL

[Brian LeRoux]

So wait, the use case is proj level deps not plugin level?
On Oct 1, 2013 10:50 PM, "Andrew Grieve"  wrote:

> There is a need to have plugman look in places other than the registry when
> fetching plugins by ID. This is particularly the case because 
> plugins now have IDs only instead of specifying a URL.
>
> Downstream distributions need this (e.g. IBM packages plugins with their
> distro). But this would be nice for mobile-spec as well (dependency plugin
> could just list IDs instead of plugin paths).
>
> Idea #1:
> Add a map to a project's .cordova/config.json with explicit ID -> URL
> mappings. E.g.:
> "plugin_map": {
>   "org.apache.cordova.file": "file:///some/path",
>   "org.apache.cordova.file-transfer": "http://git.com/url#hash";
> }
>
> Idea #2
> Add the idea of "plugin search path"
> e.g.:
> .cordova/config.json
>"plugin_search_path": ["file:///my/local/plugins", "
> http://my/custom/couch/db";, ""]
>
> Entries here can be:
>   1. local directory where each subdirectory contains a plugin
>   2. http:// to a couchdb of a custom registry
>   3. , which means prepend this list instead of replacing the
> setting.
>
>
> Idea #3
> Allow the user to copy / symlink the plugin sources into a projects
> plugins/ directory. The directory names in here would need to be the plugin
> IDs. When a request to install a plugin is made, plugman will first check
> if it already exists within plugins/, and if so, uses that source. It would
> also need to know not to delete the directory on plugin rm.
>
>
>
> #1 is nice because it's simple, but may not be super convenient (since you
> need to explicitly add each plugin). It's also the only suggestion that
> allows you to map an ID to a custom git URL
> #2 will work well for plugin collections, but may be annoying if you just
> want to override a single plugin location.
> #3 is arguably the most flexible since it leaves the fetching completely up
> to the user. It may encourage people to muck with their plugins/ to the
> point of breaking their project though. (e.g. they may delete plugins that
> are installed)
>
>
> I think I'd lean towards allowing both #1 and #2.
>

Re: Tagging 3.1.0 today?

[Steven Gill]

According to http://wiki.apache.org/cordova/VersioningAndReleaseStrategy,
it looks like we were leaning towards CadVer-SemVer for the CLI. I just
think it would be weird to only make it CadVer for this release and then
add on the SemVer part whenever we make little fixes for the weekly
release.


On Tue, Oct 1, 2013 at 2:46 PM, Andrew Grieve  wrote:

> On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill 
> wrote:
>
> > FFOS is tagged.
> >
> > Looks like windows platforms and blackberry have been tagged as well. I
> saw
> > the tags on the repos and went ahead and closed the issues. Let me know
> if
> > you guys didn't want those issues closed just yet.
> >
> > Only things remaining are retagging docs, tagging cli, tagging plugman,
> > uploading the release and posting the blog post.
> >
> > I merged in Jesse's windows 8 pull requests to cordova-3.1.x branches of
> > the CLI + Plugman locally on my machine. I am running into some errors
> when
> > adding windows8 as a platform. I will chat with Jesse and once that is
> > sorted, I will push the updates up to apache.
> >
> > With CLI and Plugman, do we want to increase the version from the RC? The
> > RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would make the
> > most sense to update those to 3.0.11 and 0.13.0 instead of retagging
> those
> > on npm. Thoughts?
> >
>
> Updating version makes sense to me. There is still some debate over what
> the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0") I'd
> like the former
>
>
> >
> >
> >
> >
> >
> >
> > On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:
> >
> > > Do you mind doing it? I think we've always deleted and re-tagged using
> > the
> > > same name
> > >
> > >
> > > On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard 
> > wrote:
> > >
> > > > Shaz, do you want to take care of that, or would you like me to?
> > > >
> > > > When doing a re-tag, do we do the sane thing (use a modified tag
> name)
> > or
> > > > the insane thing (reuse the same tag name)?
> > > >
> > > > Looks like you already put the change in both the en/edge and
> en/3.1.0
> > > > dirs. Nice.
> > > >
> > > > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> > > >
> > > > > Added
> > > >
> http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > > > > cordova-docs, needs a 3.1.0 re-tag.
> > > >
> > > >
> > >
> >
>

Re: Tagging 3.1.0 today?

[Jeffrey Heifetz]

David Kemp's buoldbot found a bug in cli from the plugman bump. I have a fix 
upcoming

Sent from my BlackBerry 10 smartphone on the Rogers network.
From: Andrew Grieve
Sent: Tuesday, October 1, 2013 5:47 PM
To: dev
Reply To: dev@cordova.apache.org
Subject: Re: Tagging 3.1.0 today?


On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill  wrote:

> FFOS is tagged.
>
> Looks like windows platforms and blackberry have been tagged as well. I saw
> the tags on the repos and went ahead and closed the issues. Let me know if
> you guys didn't want those issues closed just yet.
>
> Only things remaining are retagging docs, tagging cli, tagging plugman,
> uploading the release and posting the blog post.
>
> I merged in Jesse's windows 8 pull requests to cordova-3.1.x branches of
> the CLI + Plugman locally on my machine. I am running into some errors when
> adding windows8 as a platform. I will chat with Jesse and once that is
> sorted, I will push the updates up to apache.
>
> With CLI and Plugman, do we want to increase the version from the RC? The
> RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would make the
> most sense to update those to 3.0.11 and 0.13.0 instead of retagging those
> on npm. Thoughts?
>

Updating version makes sense to me. There is still some debate over what
the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0") I'd
like the former


>
>
>
>
>
>
> On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:
>
> > Do you mind doing it? I think we've always deleted and re-tagged using
> the
> > same name
> >
> >
> > On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard 
> wrote:
> >
> > > Shaz, do you want to take care of that, or would you like me to?
> > >
> > > When doing a re-tag, do we do the sane thing (use a modified tag name)
> or
> > > the insane thing (reuse the same tag name)?
> > >
> > > Looks like you already put the change in both the en/edge and en/3.1.0
> > > dirs. Nice.
> > >
> > > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> > >
> > > > Added
> > > http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > > > cordova-docs, needs a 3.1.0 re-tag.
> > >
> > >
> >
>
-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

Re: Tagging 3.1.0 today?

[Andrew Grieve]

On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill  wrote:

> FFOS is tagged.
>
> Looks like windows platforms and blackberry have been tagged as well. I saw
> the tags on the repos and went ahead and closed the issues. Let me know if
> you guys didn't want those issues closed just yet.
>
> Only things remaining are retagging docs, tagging cli, tagging plugman,
> uploading the release and posting the blog post.
>
> I merged in Jesse's windows 8 pull requests to cordova-3.1.x branches of
> the CLI + Plugman locally on my machine. I am running into some errors when
> adding windows8 as a platform. I will chat with Jesse and once that is
> sorted, I will push the updates up to apache.
>
> With CLI and Plugman, do we want to increase the version from the RC? The
> RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would make the
> most sense to update those to 3.0.11 and 0.13.0 instead of retagging those
> on npm. Thoughts?
>

Updating version makes sense to me. There is still some debate over what
the CLI version should look like I think ("3.1.0" vs "3.1.0-0.1.0") I'd
like the former


>
>
>
>
>
>
> On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:
>
> > Do you mind doing it? I think we've always deleted and re-tagged using
> the
> > same name
> >
> >
> > On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard 
> wrote:
> >
> > > Shaz, do you want to take care of that, or would you like me to?
> > >
> > > When doing a re-tag, do we do the sane thing (use a modified tag name)
> or
> > > the insane thing (reuse the same tag name)?
> > >
> > > Looks like you already put the change in both the en/edge and en/3.1.0
> > > dirs. Nice.
> > >
> > > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> > >
> > > > Added
> > > http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > > > cordova-docs, needs a 3.1.0 re-tag.
> > >
> > >
> >
>

Mapping plugin ID -> URL

[Andrew Grieve]

There is a need to have plugman look in places other than the registry when
fetching plugins by ID. This is particularly the case because 
plugins now have IDs only instead of specifying a URL.

Downstream distributions need this (e.g. IBM packages plugins with their
distro). But this would be nice for mobile-spec as well (dependency plugin
could just list IDs instead of plugin paths).

Idea #1:
Add a map to a project's .cordova/config.json with explicit ID -> URL
mappings. E.g.:
"plugin_map": {
  "org.apache.cordova.file": "file:///some/path",
  "org.apache.cordova.file-transfer": "http://git.com/url#hash";
}

Idea #2
Add the idea of "plugin search path"
e.g.:
.cordova/config.json
   "plugin_search_path": ["file:///my/local/plugins", "
http://my/custom/couch/db";, ""]

Entries here can be:
  1. local directory where each subdirectory contains a plugin
  2. http:// to a couchdb of a custom registry
  3. , which means prepend this list instead of replacing the
setting.


Idea #3
Allow the user to copy / symlink the plugin sources into a projects
plugins/ directory. The directory names in here would need to be the plugin
IDs. When a request to install a plugin is made, plugman will first check
if it already exists within plugins/, and if so, uses that source. It would
also need to know not to delete the directory on plugin rm.



#1 is nice because it's simple, but may not be super convenient (since you
need to explicitly add each plugin). It's also the only suggestion that
allows you to map an ID to a custom git URL
#2 will work well for plugin collections, but may be annoying if you just
want to override a single plugin location.
#3 is arguably the most flexible since it leaves the fetching completely up
to the user. It may encourage people to muck with their plugins/ to the
point of breaking their project though. (e.g. they may delete plugins that
are installed)


I think I'd lean towards allowing both #1 and #2.

Re: Tagging 3.1.0 today?

[Steven Gill]

FFOS is tagged.

Looks like windows platforms and blackberry have been tagged as well. I saw
the tags on the repos and went ahead and closed the issues. Let me know if
you guys didn't want those issues closed just yet.

Only things remaining are retagging docs, tagging cli, tagging plugman,
uploading the release and posting the blog post.

I merged in Jesse's windows 8 pull requests to cordova-3.1.x branches of
the CLI + Plugman locally on my machine. I am running into some errors when
adding windows8 as a platform. I will chat with Jesse and once that is
sorted, I will push the updates up to apache.

With CLI and Plugman, do we want to increase the version from the RC? The
RC for CLI is 3.0.10 and for plugman is 0.12.0. I think it would make the
most sense to update those to 3.0.11 and 0.13.0 instead of retagging those
on npm. Thoughts?






On Tue, Oct 1, 2013 at 2:10 PM, Shazron  wrote:

> Do you mind doing it? I think we've always deleted and re-tagged using the
> same name
>
>
> On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard  wrote:
>
> > Shaz, do you want to take care of that, or would you like me to?
> >
> > When doing a re-tag, do we do the sane thing (use a modified tag name) or
> > the insane thing (reuse the same tag name)?
> >
> > Looks like you already put the change in both the en/edge and en/3.1.0
> > dirs. Nice.
> >
> > On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
> >
> > > Added
> > http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > > cordova-docs, needs a 3.1.0 re-tag.
> >
> >
>

Re: Tagging 3.1.0 today?

[Shazron]

Do you mind doing it? I think we've always deleted and re-tagged using the
same name


On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard  wrote:

> Shaz, do you want to take care of that, or would you like me to?
>
> When doing a re-tag, do we do the sane thing (use a modified tag name) or
> the insane thing (reuse the same tag name)?
>
> Looks like you already put the change in both the en/edge and en/3.1.0
> dirs. Nice.
>
> On Oct 1, 2013, at 4:16 PM, Shazron  wrote:
>
> > Added
> http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> > cordova-docs, needs a 3.1.0 re-tag.
>
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

Shaz, do you want to take care of that, or would you like me to? 

When doing a re-tag, do we do the sane thing (use a modified tag name) or the 
insane thing (reuse the same tag name)?

Looks like you already put the change in both the en/edge and en/3.1.0 dirs. 
Nice.

On Oct 1, 2013, at 4:16 PM, Shazron  wrote:

> Added http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
> cordova-docs, needs a 3.1.0 re-tag.

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Yeah, I think cherry-picking would be the way to go.

You'll also want to add url= and subdir= attributes to the 
tags within the plugins, or else installing them will hit the registry for
the dependents (this is the current case).

I'd like to add a way to have a local map of plugin ID -> local directory
to address this shortcoming, but it's still a TODO.


On Tue, Oct 1, 2013 at 9:36 PM, Marcel Kinard  wrote:

> I could cherrypick Shaz's fix into my snapshot if doing a plugin release
> tomorrow would be undesireable.
>
> On Oct 1, 2013, at 4:00 PM, Marcel Kinard  wrote:
>
> > For my customers, splashscreen is pretty important. How about doing the
> plugin release tomorrow, at least for this plugin?
>
>

Re: Tagging 3.1.0 today?

[Bryan Higgins]

Here is the BB write-up.

There have been 48 commits to the BlackBerry platform since 3.0.0. Many
performance and stability improvements were introduced. Other notable
changes include:

[CB-4876](https://issues.apache.org/jira/browse/CB-4876) removal of
playbook implementation
[CB-4812](https://issues.apache.org/jira/browse/CB-4812) Support for
"default" value in the orientation preference
[CB-4544](https://issues.apache.org/jira/browse/CB-4544) Adds a --query
flag to query the user for their password when we need it
[CB-4563](https://issues.apache.org/jira/browse/CB-4563) Migrated
blackberry.app parameters to preferences
[CB-4344](https://issues.apache.org/jira/browse/CB-4344) Auto-detect
started simulator
[CB-4342](https://issues.apache.org/jira/browse/CB-4342) Detect USB
connected device
[CB-4076](https://issues.apache.org/jira/browse/CB-4076) Modified
config-parser to default to the uri attribute


On Tue, Oct 1, 2013 at 4:17 PM, Steven Gill  wrote:

> I shall do FFOS tag + write up
>
>
> On Tue, Oct 1, 2013 at 1:15 PM, Bryan Higgins  >wrote:
>
> > I will write up the BlackBerry notes.
> >
> >
> > On Tue, Oct 1, 2013 at 4:12 PM, Jesse  wrote:
> >
> > > windows8, windows phone 7 + 8 all updated and tagged.
> > > I will have some info to add to the blog post for these platforms
> > shortly.
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > >
> > > On Tue, Oct 1, 2013 at 1:04 PM, Shazron  wrote:
> > >
> > > > iOS tagged. I'm updating the iOS Upgrade Guide to include the default
> > > > compiler thing, then I'm working on updating the iOS splashscreen
> code,
> > > > then testing.
> > > >
> > > >
> > > > On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard 
> > > wrote:
> > > >
> > > > > For my customers, splashscreen is pretty important. How about doing
> > the
> > > > > plugin release tomorrow, at least for this plugin?
> > > > >
> > > > > +1 for Media set-position being published at a later time.
> > > > >
> > > > > On Oct 1, 2013, at 3:46 PM, Steven Gill 
> > > wrote:
> > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > If you feel the changes need to get in ASAP, we can bump up the
> > > plugin
> > > > > > release to tomorrow. Nothing like two plugin releases in one week
> > :P
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

I could cherrypick Shaz's fix into my snapshot if doing a plugin release 
tomorrow would be undesireable.

On Oct 1, 2013, at 4:00 PM, Marcel Kinard  wrote:

> For my customers, splashscreen is pretty important. How about doing the 
> plugin release tomorrow, at least for this plugin?

Re: Tagging 3.1.0 today?

[Shazron]

ios splashscreen re-fix tested and pushed to dev.


On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard  wrote:

> For my customers, splashscreen is pretty important. How about doing the
> plugin release tomorrow, at least for this plugin?
>
> +1 for Media set-position being published at a later time.
>
> On Oct 1, 2013, at 3:46 PM, Steven Gill  wrote:
>
> > Thoughts?
> >
> > If you feel the changes need to get in ASAP, we can bump up the plugin
> > release to tomorrow. Nothing like two plugin releases in one week :P
>
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

The plugins get distributed by us with the platforms. So I'm creating a static 
snapshot. The customer's environment does not do a fetch from repository/git. 
This is why I'm interested in having a "good point in time".

On Oct 1, 2013, at 4:04 PM, Andrew Grieve  wrote:

> Marcel - just want to better understand what you're doing -
> 
> Are you distributing the plugins yourself? Or are you having your customers
> get them from the plugin repository / git URL?

Re: Tagging 3.1.0 today?

[Shazron]

Added http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato
cordova-docs, needs a 3.1.0 re-tag.


On Tue, Oct 1, 2013 at 1:12 PM, Jesse  wrote:

> windows8, windows phone 7 + 8 all updated and tagged.
> I will have some info to add to the blog post for these platforms shortly.
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Oct 1, 2013 at 1:04 PM, Shazron  wrote:
>
> > iOS tagged. I'm updating the iOS Upgrade Guide to include the default
> > compiler thing, then I'm working on updating the iOS splashscreen code,
> > then testing.
> >
> >
> > On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard 
> wrote:
> >
> > > For my customers, splashscreen is pretty important. How about doing the
> > > plugin release tomorrow, at least for this plugin?
> > >
> > > +1 for Media set-position being published at a later time.
> > >
> > > On Oct 1, 2013, at 3:46 PM, Steven Gill 
> wrote:
> > >
> > > > Thoughts?
> > > >
> > > > If you feel the changes need to get in ASAP, we can bump up the
> plugin
> > > > release to tomorrow. Nothing like two plugin releases in one week :P
> > >
> > >
> >
>

Re: Tagging 3.1.0 today?

[Steven Gill]

I shall do FFOS tag + write up


On Tue, Oct 1, 2013 at 1:15 PM, Bryan Higgins wrote:

> I will write up the BlackBerry notes.
>
>
> On Tue, Oct 1, 2013 at 4:12 PM, Jesse  wrote:
>
> > windows8, windows phone 7 + 8 all updated and tagged.
> > I will have some info to add to the blog post for these platforms
> shortly.
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Oct 1, 2013 at 1:04 PM, Shazron  wrote:
> >
> > > iOS tagged. I'm updating the iOS Upgrade Guide to include the default
> > > compiler thing, then I'm working on updating the iOS splashscreen code,
> > > then testing.
> > >
> > >
> > > On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard 
> > wrote:
> > >
> > > > For my customers, splashscreen is pretty important. How about doing
> the
> > > > plugin release tomorrow, at least for this plugin?
> > > >
> > > > +1 for Media set-position being published at a later time.
> > > >
> > > > On Oct 1, 2013, at 3:46 PM, Steven Gill 
> > wrote:
> > > >
> > > > > Thoughts?
> > > > >
> > > > > If you feel the changes need to get in ASAP, we can bump up the
> > plugin
> > > > > release to tomorrow. Nothing like two plugin releases in one week
> :P
> > > >
> > > >
> > >
> >
>

Re: Tag 2.9.1

[Ian Clelland]

Right. I wasn't sure if there were 10 issues to backport or 150. If there
are only a few isolated fixes to apply, then I'd be comfortable with just
applying them, testing and releasing. If there are a ton of fixes, which
might have overlapping effects, then lets spend a day or so with a tagged
rc and have everybody test the same finished product before we ship it.

Ian

On Tuesday, October 1, 2013, Jesse wrote:

> Nope, I don't think we've ever done minor rc's, this is a bit more of a
> significant release though.
> Back-fill would just be putting all the updated plugin native code back
> into each platform, as well as making sure any relevant js changes went
> back into cordova-js before being tagged+built.  Kind of a hassle, with no
> easy way of making sure things aren't missed, other than mobile-spec.
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Oct 1, 2013 at 12:32 PM, Ian Clelland 
> 
> >wrote:
>
> > Have we done RCs for minor releases before? I don't recall any for 3.0.1
> to
> > 3.0.9, and I can't see anything in my email archives from 2.6.1 or 2.8.1.
> >
> > Not that it's a bad idea; I just don't think it's a formality that has
> been
> > observed in the past.
> >
> > How much back-fill are you expecting?
> >
> >
> >
> >
> > On Tue, Oct 1, 2013 at 2:50 PM, Jesse 
> > >
> wrote:
> >
> > > As soon as we are done with 3.1.0 it would be a good time to go back
> and
> > > back-fill for a 2,9,1 release.
> > >
> > > Who's with me?
> > > Do we need to do an RC? If so, a quick one?
> > >
> > > Cheers,
> > >   Jesse
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> >
>

Re: Tagging 3.1.0 today?

[Bryan Higgins]

I will write up the BlackBerry notes.


On Tue, Oct 1, 2013 at 4:12 PM, Jesse  wrote:

> windows8, windows phone 7 + 8 all updated and tagged.
> I will have some info to add to the blog post for these platforms shortly.
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Oct 1, 2013 at 1:04 PM, Shazron  wrote:
>
> > iOS tagged. I'm updating the iOS Upgrade Guide to include the default
> > compiler thing, then I'm working on updating the iOS splashscreen code,
> > then testing.
> >
> >
> > On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard 
> wrote:
> >
> > > For my customers, splashscreen is pretty important. How about doing the
> > > plugin release tomorrow, at least for this plugin?
> > >
> > > +1 for Media set-position being published at a later time.
> > >
> > > On Oct 1, 2013, at 3:46 PM, Steven Gill 
> wrote:
> > >
> > > > Thoughts?
> > > >
> > > > If you feel the changes need to get in ASAP, we can bump up the
> plugin
> > > > release to tomorrow. Nothing like two plugin releases in one week :P
> > >
> > >
> >
>

Re: Tagging 3.1.0 today?

[Jesse]

windows8, windows phone 7 + 8 all updated and tagged.
I will have some info to add to the blog post for these platforms shortly.

@purplecabbage
risingj.com


On Tue, Oct 1, 2013 at 1:04 PM, Shazron  wrote:

> iOS tagged. I'm updating the iOS Upgrade Guide to include the default
> compiler thing, then I'm working on updating the iOS splashscreen code,
> then testing.
>
>
> On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard  wrote:
>
> > For my customers, splashscreen is pretty important. How about doing the
> > plugin release tomorrow, at least for this plugin?
> >
> > +1 for Media set-position being published at a later time.
> >
> > On Oct 1, 2013, at 3:46 PM, Steven Gill  wrote:
> >
> > > Thoughts?
> > >
> > > If you feel the changes need to get in ASAP, we can bump up the plugin
> > > release to tomorrow. Nothing like two plugin releases in one week :P
> >
> >
>

Re: Tag 2.9.1

[Jesse]

Nope, I don't think we've ever done minor rc's, this is a bit more of a
significant release though.
Back-fill would just be putting all the updated plugin native code back
into each platform, as well as making sure any relevant js changes went
back into cordova-js before being tagged+built.  Kind of a hassle, with no
easy way of making sure things aren't missed, other than mobile-spec.



@purplecabbage
risingj.com


On Tue, Oct 1, 2013 at 12:32 PM, Ian Clelland wrote:

> Have we done RCs for minor releases before? I don't recall any for 3.0.1 to
> 3.0.9, and I can't see anything in my email archives from 2.6.1 or 2.8.1.
>
> Not that it's a bad idea; I just don't think it's a formality that has been
> observed in the past.
>
> How much back-fill are you expecting?
>
>
>
>
> On Tue, Oct 1, 2013 at 2:50 PM, Jesse  wrote:
>
> > As soon as we are done with 3.1.0 it would be a good time to go back and
> > back-fill for a 2,9,1 release.
> >
> > Who's with me?
> > Do we need to do an RC? If so, a quick one?
> >
> > Cheers,
> >   Jesse
> >
> > @purplecabbage
> > risingj.com
> >
>

Re: Tagging 3.1.0 today?

[Shazron]

iOS tagged. I'm updating the iOS Upgrade Guide to include the default
compiler thing, then I'm working on updating the iOS splashscreen code,
then testing.


On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard  wrote:

> For my customers, splashscreen is pretty important. How about doing the
> plugin release tomorrow, at least for this plugin?
>
> +1 for Media set-position being published at a later time.
>
> On Oct 1, 2013, at 3:46 PM, Steven Gill  wrote:
>
> > Thoughts?
> >
> > If you feel the changes need to get in ASAP, we can bump up the plugin
> > release to tomorrow. Nothing like two plugin releases in one week :P
>
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Marcel - just want to better understand what you're doing -

Are you distributing the plugins yourself? Or are you having your customers
get them from the plugin repository / git URL?


On Tue, Oct 1, 2013 at 9:00 PM, Marcel Kinard  wrote:

> For my customers, splashscreen is pretty important. How about doing the
> plugin release tomorrow, at least for this plugin?
>
> +1 for Media set-position being published at a later time.
>
> On Oct 1, 2013, at 3:46 PM, Steven Gill  wrote:
>
> > Thoughts?
> >
> > If you feel the changes need to get in ASAP, we can bump up the plugin
> > release to tomorrow. Nothing like two plugin releases in one week :P
>
>

Re: ios commit: Delete some incorrect RELEASENOTES.md entries

[Andrew Grieve]

I think likely those were the cherry-picks.


On Tue, Oct 1, 2013 at 8:54 PM, Shazron  wrote:

> Not sure why those are in there, I specified 3.0.0...3.1.x
>
>
> On Tue, Oct 1, 2013 at 12:29 PM,  wrote:
>
> > Updated Branches:
> >   refs/heads/master cc01343e1 -> 246f8e56c
> >
> >
> > Delete some incorrect RELEASENOTES.md entries
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/cordova-ios/repo
> > Commit:
> http://git-wip-us.apache.org/repos/asf/cordova-ios/commit/246f8e56
> > Tree: http://git-wip-us.apache.org/repos/asf/cordova-ios/tree/246f8e56
> > Diff: http://git-wip-us.apache.org/repos/asf/cordova-ios/diff/246f8e56
> >
> > Branch: refs/heads/master
> > Commit: 246f8e56c789418fc92d542880196fd2aba0f485
> > Parents: cc01343
> > Author: Andrew Grieve 
> > Authored: Tue Oct 1 15:29:32 2013 -0400
> > Committer: Andrew Grieve 
> > Committed: Tue Oct 1 15:29:32 2013 -0400
> >
> > --
> >  RELEASENOTES.md | 5 -
> >  1 file changed, 5 deletions(-)
> > --
> >
> >
> >
> >
> http://git-wip-us.apache.org/repos/asf/cordova-ios/blob/246f8e56/RELEASENOTES.md
> > --
> > diff --git a/RELEASENOTES.md b/RELEASENOTES.md
> > index 8b00de5..9b74cf4 100644
> > --- a/RELEASENOTES.md
> > +++ b/RELEASENOTES.md
> > @@ -64,11 +64,6 @@ Cordova is a static library that enables developers to
> > include the Cordova API i
> >  * [CB-4281] Moving echo to a plugin in MobileSpec
> >  * [CB-4277] Revert deleting of  />
> > support
> >  * [CB-3005] Add support for query parameters in StartPage url
> > -* [CB-4133] iOS detection of plugins that run long on main thread
> > -* [CB-4277] onload (boolean) attribute of config.xml param tag is
> ignored
> > -* [CB-4277] Revert deleting of  />
> > support
> > -* [CB-4133] iOS detection of plugins that run long on main thread
> > -* [CB-4277] onload (boolean) attribute of config.xml param tag is
> ignored
> >  * CordovaTests project was missing the CordovaLib dependency: added
> >  * Update iOS whitelist tests
> >  * Fix ARC issue in start page tests (critical for Xcode5)
> >
> >
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

For my customers, splashscreen is pretty important. How about doing the plugin 
release tomorrow, at least for this plugin?

+1 for Media set-position being published at a later time.

On Oct 1, 2013, at 3:46 PM, Steven Gill  wrote:

> Thoughts?
> 
> If you feel the changes need to get in ASAP, we can bump up the plugin
> release to tomorrow. Nothing like two plugin releases in one week :P

Re: ios commit: Delete some incorrect RELEASENOTES.md entries

[Shazron]

Not sure why those are in there, I specified 3.0.0...3.1.x


On Tue, Oct 1, 2013 at 12:29 PM,  wrote:

> Updated Branches:
>   refs/heads/master cc01343e1 -> 246f8e56c
>
>
> Delete some incorrect RELEASENOTES.md entries
>
>
> Project: http://git-wip-us.apache.org/repos/asf/cordova-ios/repo
> Commit: http://git-wip-us.apache.org/repos/asf/cordova-ios/commit/246f8e56
> Tree: http://git-wip-us.apache.org/repos/asf/cordova-ios/tree/246f8e56
> Diff: http://git-wip-us.apache.org/repos/asf/cordova-ios/diff/246f8e56
>
> Branch: refs/heads/master
> Commit: 246f8e56c789418fc92d542880196fd2aba0f485
> Parents: cc01343
> Author: Andrew Grieve 
> Authored: Tue Oct 1 15:29:32 2013 -0400
> Committer: Andrew Grieve 
> Committed: Tue Oct 1 15:29:32 2013 -0400
>
> --
>  RELEASENOTES.md | 5 -
>  1 file changed, 5 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/cordova-ios/blob/246f8e56/RELEASENOTES.md
> --
> diff --git a/RELEASENOTES.md b/RELEASENOTES.md
> index 8b00de5..9b74cf4 100644
> --- a/RELEASENOTES.md
> +++ b/RELEASENOTES.md
> @@ -64,11 +64,6 @@ Cordova is a static library that enables developers to
> include the Cordova API i
>  * [CB-4281] Moving echo to a plugin in MobileSpec
>  * [CB-4277] Revert deleting of 
> support
>  * [CB-3005] Add support for query parameters in StartPage url
> -* [CB-4133] iOS detection of plugins that run long on main thread
> -* [CB-4277] onload (boolean) attribute of config.xml param tag is ignored
> -* [CB-4277] Revert deleting of 
> support
> -* [CB-4133] iOS detection of plugins that run long on main thread
> -* [CB-4277] onload (boolean) attribute of config.xml param tag is ignored
>  * CordovaTests project was missing the CordovaLib dependency: added
>  * Update iOS whitelist tests
>  * Fix ARC issue in start page tests (critical for Xcode5)
>
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Blog post drafted, but it's missing highlights for Windows Phone,
BlackBerry and FFOS (I based them on RELEASENOTES.md). Can I have
volunteers to write up those sections?

https://reviews.apache.org/r/14429/


On Tue, Oct 1, 2013 at 8:52 PM, Andrew Grieve  wrote:

> Awesome! FYI - I tweaked the "rake build" and "rake serve" logic today to
> not suck so much. It will no longer delete .svn directories, and `serve`
> will now never overwrite files within public/. Let me know if you have
> issues.
>
>
> On Tue, Oct 1, 2013 at 8:37 PM, Steven Gill wrote:
>
>> Yup! Plugins got released last week. I will be posting the blog for it
>> today.
>>
>> Once platforms are tagged, I can look into assembling the distribution.
>>
>>
>> On Tue, Oct 1, 2013 at 12:34 PM, Andrew Grieve 
>> wrote:
>>
>> > Steve should clarify - but I think he did a plugins release last week
>> and
>> > just needs to upload the blog post for it?
>> >
>> >
>> > On Tue, Oct 1, 2013 at 8:32 PM, Marcel Kinard 
>> wrote:
>> >
>> > > Just curious, will there be a plugins release today to coincide, or
>> will
>> > > that be done on a different date (and if so, what day, Thursday)?
>> >
>>
>
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Awesome! FYI - I tweaked the "rake build" and "rake serve" logic today to
not suck so much. It will no longer delete .svn directories, and `serve`
will now never overwrite files within public/. Let me know if you have
issues.


On Tue, Oct 1, 2013 at 8:37 PM, Steven Gill  wrote:

> Yup! Plugins got released last week. I will be posting the blog for it
> today.
>
> Once platforms are tagged, I can look into assembling the distribution.
>
>
> On Tue, Oct 1, 2013 at 12:34 PM, Andrew Grieve 
> wrote:
>
> > Steve should clarify - but I think he did a plugins release last week and
> > just needs to upload the blog post for it?
> >
> >
> > On Tue, Oct 1, 2013 at 8:32 PM, Marcel Kinard 
> wrote:
> >
> > > Just curious, will there be a plugins release today to coincide, or
> will
> > > that be done on a different date (and if so, what day, Thursday)?
> >
>

Re: Plugman Release

[Steven Gill]

the branch for both CLI and Plugman is called cordova-3.1.x (don't know why
we didn't call it 3.1.x instead)


On Tue, Oct 1, 2013 at 12:04 PM, Jeffrey Heifetz wrote:

> It seems as though there is no cordova-cli 3.1.x branch, does this mean we
> always release off of master?
>
> There is a bug I found where element tree needs to be bumped to the same
> version as plugman to support namespace xml elements and I'd like to know
> where to push this.
>
> Thanks,
>
> Jeff
>
> On 13-10-01 12:17 PM, "Steven Gill"  wrote:
>
> >Firefoxos is broken on master after the refactor. It works fine on the
> >cordova-3.1.x branch though.
> >
> >I am testing jesse's pull requests for CLI + plugman today for
> >cordova-3.1.x branch. If they look good I will merge them in. We should
> >release CLI + Plugman at the same time as 3.1.0. The release should be
> >based off cordova-3.1.x branch and not master.
> >On Oct 1, 2013 7:41 AM, "Andrew Grieve"  wrote:
> >
> >> Braden's out doing intern interviews yesterday & today, so it's unlikely
> >> he'll see this email until tomorrow if not Thursday.
> >>
> >> We could still do a tools release, but just don't update the
> >>platforms.js
> >> file to point at 3.1.0. That said, I think I saw Firefox was broken on
> >> HEAD? Think we'll want to fix that before doing so.
> >>
> >> In terms of testing the RC - as Steven said - using cordova@3.0.10
> >>should
> >> do the trick
> >>
> >>
> >> On Tue, Oct 1, 2013 at 2:22 AM, Jesse  wrote:
> >>
> >> > I have an open pull request I would like someone else to look at. [1]
> >> > This addresses the issue that Carlos brought up during plugin remove
> >>[2]
> >> > It would be great if this could be part of the release, or at least
> >>the
> >> > commit cherry picked into it.
> >> >
> >> > Cheers,
> >> >   Jesse
> >> >
> >> >
> >> >
> >> > [1]
> >> > https://github.com/purplecabbage/cordova-plugman/pull/2
> >> > [2]
> >> > https://issues.apache.org/jira/browse/CB-4943
> >> >
> >> >
> >> >
> >> >
> >> > @purplecabbage
> >> > risingj.com
> >> >
> >> >
> >> > On Mon, Sep 30, 2013 at 4:12 PM, Steven Gill 
> >> > wrote:
> >> >
> >> > > I believe Braden did the same type of release for plugman that he
> >>did
> >> for
> >> > > cordova cli. He updated both packages on npm but set the latest tag
> >>to
> >> > > point to the previous version until we were ready to do our full
> >> release.
> >> > >
> >> > > If you install the CLI RC
> >> > > sudo npm install -g cordova@3.0.10, you actually get version 0.12.0
> >>of
> >> > > plugman as a dependency.
> >> > >
> >> > > I will wait for Braden to chime in. I figure the CLI and Plugman
> >>should
> >> > > both be released on the same day we release 3.1.0.
> >> > >
> >> > >
> >> > >
> >> > > On Mon, Sep 30, 2013 at 1:39 PM, David Kemp 
> >>wrote:
> >> > >
> >> > > > +1  to a plugman npm release.
> >> > > >
> >> > > > David Kemp
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Mon, Sep 30, 2013 at 4:34 PM, Steven Gill
> >> >> >
> >> > > > wrote:
> >> > > >
> >> > > > > Anyone see any issue with me doing a npm plugman release today?
> >> > Testing
> >> > > > the
> >> > > > > CLI RC is kind of weird when the plugman dependency is
> >> incompatible.
> >> > > > >
> >> > > > > -Steve
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
>
> -
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
>

Re: Tagging 3.1.0 today?

[Shazron]

Alright - i'll just checkin to dev, and let's worry about the decision for
an updated plugin release for later.


On Tue, Oct 1, 2013 at 12:46 PM, Steven Gill  wrote:

> I would suggest doing all of your work in dev and don't worry about cherry
> picking into master. We can do another plugin release early next week where
> we merge into master, tag and reupload to plugins.cordova.io. We did plan
> on doing a release on a weekly basis if I recall correctly.
>
> Thoughts?
>
> If you feel the changes need to get in ASAP, we can bump up the plugin
> release to tomorrow. Nothing like two plugin releases in one week :P
>
> -Steve
>
>
> On Tue, Oct 1, 2013 at 12:39 PM, Shazron  wrote:
>
> > One failure in Media plugin (set position) for both iOS 6 and 7. Should
> > this hold the release up? I would say no since we can always update the
> > plugin.
> >
> > Unfortunately the splashscreen plugin has a typo (my bad) that results
> in a
> > visual failure on iOS 6 (decrementing a value twice):
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;a=blobdiff;f=src/ios/CDVSplashScreen.m;h=8159ce17bda7a4d10277aa4cbc132fa2c8e6e39d;hp=ba8d108b725f1a1d2331f8e8fc56627aac929ba5;hb=c8b3b9b8fe28d6c9fe9c9a1bc548a679e4ac;hpb=5f83eda5e829ac7a11e1803de653cb7cf95764af
> >
> > I will have to patch that in dev and probably cherry-pick(?) into master
> -
> > how will this go?
> >
> > iOS 6
> > one failure - Media media.spec.12 position should be set properly
> > Expected 0 to be greater than 0
> >
> > iOS 7
> > one failure - Media media.spec.12 position should be set properly
> > Expected -0.023 to be greater than 0
> >
> >
> >
> > On Tue, Oct 1, 2013 at 11:27 AM, Shazron  wrote:
> >
> > > Going to tag iOS within the next hour.
> > >
> > >
> > > On Tuesday, October 1, 2013, Joe Bowser wrote:
> > >
> > >> Just tagged Android.  There's some weird inconsistencies across
> > >> devices, but overall the platform itself still seems solid.  There's
> > >> nothing here that would prevent a release.
> > >>
> > >> We should really start that API audit though.  These inconsistencies
> > >> don't make me super confident in the plugins. :(
> > >>
> > >> On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
> > >>  wrote:
> > >> > Since I believe Lorin is away, I have tagged the release for
> > blackberry.
> > >> >
> > >> > On 13-10-01 1:01 PM, "Marcel Kinard"  wrote:
> > >> >
> > >> >>If any platform owners don't have time to do this today, let me know
> > how
> > >> >>I can help.
> > >> >>
> > >> >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve 
> > >> wrote:
> > >> >>
> > >> >>> I think all that needs
> > >> >>> to happen now is for all platform owners to update their JS
> snapshot
> > >> >>>again
> > >> >>> and push a "3.1.0" tag.
> > >> >>
> > >> >
> > >> >
> -
> > >> > This transmission (including any attachments) may contain
> confidential
> > >> information, privileged material (including material protected by the
> > >> solicitor-client or other applicable privileges), or constitute
> > non-public
> > >> information. Any use of this information by anyone other than the
> > intended
> > >> recipient is prohibited. If you have received this transmission in
> > error,
> > >> please immediately reply to the sender and delete this information
> from
> > >> your system. Use, dissemination, distribution, or reproduction of this
> > >> transmission by unintended recipients is not authorized and may be
> > unlawful.
> > >> >
> > >>
> > >
> >
>

Review Request 14429: 3.1 release blog post

[Andrew Grieve]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14429/
---

Review request for cordova.


Repository: cordova-site


Description
---

3.1 release blog post


Diffs
-

  /cordova/site/www/_posts/2013-10-01-cordova-31.md PRE-CREATION 

Diff: https://reviews.apache.org/r/14429/diff/


Testing
---


Thanks,

Andrew Grieve

Re: Tagging 3.1.0 today?

[Ian Clelland]

On Tue, Oct 1, 2013 at 3:39 PM, Shazron  wrote:

> One failure in Media plugin (set position) for both iOS 6 and 7. Should
> this hold the release up? I would say no since we can always update the
> plugin.
>

Agreed -- plugins should be independent of core; we can fix this soon and
release cordova-plugin-media later this week.

Ian

Re: Tagging 3.1.0 today?

[Steven Gill]

I would suggest doing all of your work in dev and don't worry about cherry
picking into master. We can do another plugin release early next week where
we merge into master, tag and reupload to plugins.cordova.io. We did plan
on doing a release on a weekly basis if I recall correctly.

Thoughts?

If you feel the changes need to get in ASAP, we can bump up the plugin
release to tomorrow. Nothing like two plugin releases in one week :P

-Steve


On Tue, Oct 1, 2013 at 12:39 PM, Shazron  wrote:

> One failure in Media plugin (set position) for both iOS 6 and 7. Should
> this hold the release up? I would say no since we can always update the
> plugin.
>
> Unfortunately the splashscreen plugin has a typo (my bad) that results in a
> visual failure on iOS 6 (decrementing a value twice):
>
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;a=blobdiff;f=src/ios/CDVSplashScreen.m;h=8159ce17bda7a4d10277aa4cbc132fa2c8e6e39d;hp=ba8d108b725f1a1d2331f8e8fc56627aac929ba5;hb=c8b3b9b8fe28d6c9fe9c9a1bc548a679e4ac;hpb=5f83eda5e829ac7a11e1803de653cb7cf95764af
>
> I will have to patch that in dev and probably cherry-pick(?) into master -
> how will this go?
>
> iOS 6
> one failure - Media media.spec.12 position should be set properly
> Expected 0 to be greater than 0
>
> iOS 7
> one failure - Media media.spec.12 position should be set properly
> Expected -0.023 to be greater than 0
>
>
>
> On Tue, Oct 1, 2013 at 11:27 AM, Shazron  wrote:
>
> > Going to tag iOS within the next hour.
> >
> >
> > On Tuesday, October 1, 2013, Joe Bowser wrote:
> >
> >> Just tagged Android.  There's some weird inconsistencies across
> >> devices, but overall the platform itself still seems solid.  There's
> >> nothing here that would prevent a release.
> >>
> >> We should really start that API audit though.  These inconsistencies
> >> don't make me super confident in the plugins. :(
> >>
> >> On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
> >>  wrote:
> >> > Since I believe Lorin is away, I have tagged the release for
> blackberry.
> >> >
> >> > On 13-10-01 1:01 PM, "Marcel Kinard"  wrote:
> >> >
> >> >>If any platform owners don't have time to do this today, let me know
> how
> >> >>I can help.
> >> >>
> >> >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve 
> >> wrote:
> >> >>
> >> >>> I think all that needs
> >> >>> to happen now is for all platform owners to update their JS snapshot
> >> >>>again
> >> >>> and push a "3.1.0" tag.
> >> >>
> >> >
> >> > -
> >> > This transmission (including any attachments) may contain confidential
> >> information, privileged material (including material protected by the
> >> solicitor-client or other applicable privileges), or constitute
> non-public
> >> information. Any use of this information by anyone other than the
> intended
> >> recipient is prohibited. If you have received this transmission in
> error,
> >> please immediately reply to the sender and delete this information from
> >> your system. Use, dissemination, distribution, or reproduction of this
> >> transmission by unintended recipients is not authorized and may be
> unlawful.
> >> >
> >>
> >
>

Re: Tagging 3.1.0 today?

[Shazron]

Most of them are GCC and Clang warning settings (that are set to YES when
upgrading the project template) but they can get this upgrade when Xcode
prompts them to upgrade. The only relevant setting is changing the compiler
to "" (default) instead of hard-coding it from before:

https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=bin/templates/project/__TESTING__.xcodeproj/project.pbxproj;h=a57a3501a17d5ae585d6927f433dd7234cc6368c;hp=964c29dbaf77c26a6386c3be070b812c53b4d938;hb=4b94deba093393f0d0be3bbfc412d94fed66dd5d;hpb=f7bc24c570e3dd31d720587af2b15aed76f241cf

https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=blobdiff;f=CordovaLib/CordovaLib.xcodeproj/project.pbxproj;h=a253aaacd2dda117a237ed0b40efa95b8bcd0444;hp=17ed079ff2ea9e7180cc2ab43c53141316ce445f;hb=a71b2bdb2d79643ca16adbda2d9fed091d8db4ac;hpb=4b94deba093393f0d0be3bbfc412d94fed66dd5d

I'll add this to the Upgrade Guide (default compiler change)


On Tue, Oct 1, 2013 at 12:36 PM, Andrew Grieve  wrote:

> Shaz - there were several changes to the project template for Xcode 5. Do
> you know if any of them are necessary to mention in the upgrade guide?
>
>
> On Tue, Oct 1, 2013 at 7:27 PM, Shazron  wrote:
>
>>  Going to tag iOS within the next hour.
>>
>> On Tuesday, October 1, 2013, Joe Bowser wrote:
>>
>> > Just tagged Android.  There's some weird inconsistencies across
>> > devices, but overall the platform itself still seems solid.  There's
>> > nothing here that would prevent a release.
>> >
>> > We should really start that API audit though.  These inconsistencies
>> > don't make me super confident in the plugins. :(
>> >
>> > On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
>> > > wrote:
>> > > Since I believe Lorin is away, I have tagged the release for
>> blackberry.
>> > >
>> > > On 13-10-01 1:01 PM, "Marcel Kinard" >
>>
>> > wrote:
>> > >
>> > >>If any platform owners don't have time to do this today, let me know
>> how
>> > >>I can help.
>> > >>
>> > >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve > >
>>
>> > wrote:
>> > >>
>> > >>> I think all that needs
>> > >>> to happen now is for all platform owners to update their JS snapshot
>> > >>>again
>> > >>> and push a "3.1.0" tag.
>> > >>
>> > >
>> > > -
>> > > This transmission (including any attachments) may contain confidential
>> > information, privileged material (including material protected by the
>> > solicitor-client or other applicable privileges), or constitute
>> non-public
>> > information. Any use of this information by anyone other than the
>> intended
>> > recipient is prohibited. If you have received this transmission in
>> error,
>> > please immediately reply to the sender and delete this information from
>> > your system. Use, dissemination, distribution, or reproduction of this
>> > transmission by unintended recipients is not authorized and may be
>> unlawful.
>> > >
>> >
>>
>
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Steve should clarify - but I think he did a plugins release last week and
just needs to upload the blog post for it?


On Tue, Oct 1, 2013 at 8:32 PM, Marcel Kinard  wrote:

> Just curious, will there be a plugins release today to coincide, or will
> that be done on a different date (and if so, what day, Thursday)?

Re: Tagging 3.1.0 today?

[Shazron]

One failure in Media plugin (set position) for both iOS 6 and 7. Should
this hold the release up? I would say no since we can always update the
plugin.

Unfortunately the splashscreen plugin has a typo (my bad) that results in a
visual failure on iOS 6 (decrementing a value twice):
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;a=blobdiff;f=src/ios/CDVSplashScreen.m;h=8159ce17bda7a4d10277aa4cbc132fa2c8e6e39d;hp=ba8d108b725f1a1d2331f8e8fc56627aac929ba5;hb=c8b3b9b8fe28d6c9fe9c9a1bc548a679e4ac;hpb=5f83eda5e829ac7a11e1803de653cb7cf95764af

I will have to patch that in dev and probably cherry-pick(?) into master -
how will this go?

iOS 6
one failure - Media media.spec.12 position should be set properly
Expected 0 to be greater than 0

iOS 7
one failure - Media media.spec.12 position should be set properly
Expected -0.023 to be greater than 0



On Tue, Oct 1, 2013 at 11:27 AM, Shazron  wrote:

> Going to tag iOS within the next hour.
>
>
> On Tuesday, October 1, 2013, Joe Bowser wrote:
>
>> Just tagged Android.  There's some weird inconsistencies across
>> devices, but overall the platform itself still seems solid.  There's
>> nothing here that would prevent a release.
>>
>> We should really start that API audit though.  These inconsistencies
>> don't make me super confident in the plugins. :(
>>
>> On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
>>  wrote:
>> > Since I believe Lorin is away, I have tagged the release for blackberry.
>> >
>> > On 13-10-01 1:01 PM, "Marcel Kinard"  wrote:
>> >
>> >>If any platform owners don't have time to do this today, let me know how
>> >>I can help.
>> >>
>> >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve 
>> wrote:
>> >>
>> >>> I think all that needs
>> >>> to happen now is for all platform owners to update their JS snapshot
>> >>>again
>> >>> and push a "3.1.0" tag.
>> >>
>> >
>> > -
>> > This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-public
>> information. Any use of this information by anyone other than the intended
>> recipient is prohibited. If you have received this transmission in error,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be unlawful.
>> >
>>
>

Re: Tagging 3.1.0 today?

[Steven Gill]

Yup! Plugins got released last week. I will be posting the blog for it
today.

Once platforms are tagged, I can look into assembling the distribution.


On Tue, Oct 1, 2013 at 12:34 PM, Andrew Grieve  wrote:

> Steve should clarify - but I think he did a plugins release last week and
> just needs to upload the blog post for it?
>
>
> On Tue, Oct 1, 2013 at 8:32 PM, Marcel Kinard  wrote:
>
> > Just curious, will there be a plugins release today to coincide, or will
> > that be done on a different date (and if so, what day, Thursday)?
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Shaz - there were several changes to the project template for Xcode 5. Do
you know if any of them are necessary to mention in the upgrade guide?


On Tue, Oct 1, 2013 at 7:27 PM, Shazron  wrote:

> Going to tag iOS within the next hour.
>
> On Tuesday, October 1, 2013, Joe Bowser wrote:
>
> > Just tagged Android.  There's some weird inconsistencies across
> > devices, but overall the platform itself still seems solid.  There's
> > nothing here that would prevent a release.
> >
> > We should really start that API audit though.  These inconsistencies
> > don't make me super confident in the plugins. :(
> >
> > On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
> > > wrote:
> > > Since I believe Lorin is away, I have tagged the release for
> blackberry.
> > >
> > > On 13-10-01 1:01 PM, "Marcel Kinard" >
> > wrote:
> > >
> > >>If any platform owners don't have time to do this today, let me know
> how
> > >>I can help.
> > >>
> > >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve  >
> > wrote:
> > >>
> > >>> I think all that needs
> > >>> to happen now is for all platform owners to update their JS snapshot
> > >>>again
> > >>> and push a "3.1.0" tag.
> > >>
> > >
> > > -
> > > This transmission (including any attachments) may contain confidential
> > information, privileged material (including material protected by the
> > solicitor-client or other applicable privileges), or constitute
> non-public
> > information. Any use of this information by anyone other than the
> intended
> > recipient is prohibited. If you have received this transmission in error,
> > please immediately reply to the sender and delete this information from
> > your system. Use, dissemination, distribution, or reproduction of this
> > transmission by unintended recipients is not authorized and may be
> unlawful.
> > >
> >
>

Re: Tag 2.9.1

[Ian Clelland]

Have we done RCs for minor releases before? I don't recall any for 3.0.1 to
3.0.9, and I can't see anything in my email archives from 2.6.1 or 2.8.1.

Not that it's a bad idea; I just don't think it's a formality that has been
observed in the past.

How much back-fill are you expecting?




On Tue, Oct 1, 2013 at 2:50 PM, Jesse  wrote:

> As soon as we are done with 3.1.0 it would be a good time to go back and
> back-fill for a 2,9,1 release.
>
> Who's with me?
> Do we need to do an RC? If so, a quick one?
>
> Cheers,
>   Jesse
>
> @purplecabbage
> risingj.com
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

Just curious, will there be a plugins release today to coincide, or will that 
be done on a different date (and if so, what day, Thursday)?

Re: Plugman Release

[Jeffrey Heifetz]

It seems as though there is no cordova-cli 3.1.x branch, does this mean we
always release off of master?

There is a bug I found where element tree needs to be bumped to the same
version as plugman to support namespace xml elements and I'd like to know
where to push this.

Thanks,

Jeff

On 13-10-01 12:17 PM, "Steven Gill"  wrote:

>Firefoxos is broken on master after the refactor. It works fine on the
>cordova-3.1.x branch though.
>
>I am testing jesse's pull requests for CLI + plugman today for
>cordova-3.1.x branch. If they look good I will merge them in. We should
>release CLI + Plugman at the same time as 3.1.0. The release should be
>based off cordova-3.1.x branch and not master.
>On Oct 1, 2013 7:41 AM, "Andrew Grieve"  wrote:
>
>> Braden's out doing intern interviews yesterday & today, so it's unlikely
>> he'll see this email until tomorrow if not Thursday.
>>
>> We could still do a tools release, but just don't update the
>>platforms.js
>> file to point at 3.1.0. That said, I think I saw Firefox was broken on
>> HEAD? Think we'll want to fix that before doing so.
>>
>> In terms of testing the RC - as Steven said - using cordova@3.0.10
>>should
>> do the trick
>>
>>
>> On Tue, Oct 1, 2013 at 2:22 AM, Jesse  wrote:
>>
>> > I have an open pull request I would like someone else to look at. [1]
>> > This addresses the issue that Carlos brought up during plugin remove
>>[2]
>> > It would be great if this could be part of the release, or at least
>>the
>> > commit cherry picked into it.
>> >
>> > Cheers,
>> >   Jesse
>> >
>> >
>> >
>> > [1]
>> > https://github.com/purplecabbage/cordova-plugman/pull/2
>> > [2]
>> > https://issues.apache.org/jira/browse/CB-4943
>> >
>> >
>> >
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Mon, Sep 30, 2013 at 4:12 PM, Steven Gill 
>> > wrote:
>> >
>> > > I believe Braden did the same type of release for plugman that he
>>did
>> for
>> > > cordova cli. He updated both packages on npm but set the latest tag
>>to
>> > > point to the previous version until we were ready to do our full
>> release.
>> > >
>> > > If you install the CLI RC
>> > > sudo npm install -g cordova@3.0.10, you actually get version 0.12.0
>>of
>> > > plugman as a dependency.
>> > >
>> > > I will wait for Braden to chime in. I figure the CLI and Plugman
>>should
>> > > both be released on the same day we release 3.1.0.
>> > >
>> > >
>> > >
>> > > On Mon, Sep 30, 2013 at 1:39 PM, David Kemp 
>>wrote:
>> > >
>> > > > +1  to a plugman npm release.
>> > > >
>> > > > David Kemp
>> > > >
>> > > >
>> > > >
>> > > > On Mon, Sep 30, 2013 at 4:34 PM, Steven Gill
>>> >
>> > > > wrote:
>> > > >
>> > > > > Anyone see any issue with me doing a npm plugman release today?
>> > Testing
>> > > > the
>> > > > > CLI RC is kind of weird when the plugman dependency is
>> incompatible.
>> > > > >
>> > > > > -Steve
>> > > > >
>> > > >
>> > >
>> >
>>

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

Tag 2.9.1

[Jesse]

As soon as we are done with 3.1.0 it would be a good time to go back and
back-fill for a 2,9,1 release.

Who's with me?
Do we need to do an RC? If so, a quick one?

Cheers,
  Jesse

@purplecabbage
risingj.com

Re: Tagging 3.1.0 today?

[Shazron]

Going to tag iOS within the next hour.

On Tuesday, October 1, 2013, Joe Bowser wrote:

> Just tagged Android.  There's some weird inconsistencies across
> devices, but overall the platform itself still seems solid.  There's
> nothing here that would prevent a release.
>
> We should really start that API audit though.  These inconsistencies
> don't make me super confident in the plugins. :(
>
> On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
> > wrote:
> > Since I believe Lorin is away, I have tagged the release for blackberry.
> >
> > On 13-10-01 1:01 PM, "Marcel Kinard" >
> wrote:
> >
> >>If any platform owners don't have time to do this today, let me know how
> >>I can help.
> >>
> >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve 
> >>>
> wrote:
> >>
> >>> I think all that needs
> >>> to happen now is for all platform owners to update their JS snapshot
> >>>again
> >>> and push a "3.1.0" tag.
> >>
> >
> > -
> > This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
> >
>

Re: Tagging 3.1.0 today?

[Joe Bowser]

Just tagged Android.  There's some weird inconsistencies across
devices, but overall the platform itself still seems solid.  There's
nothing here that would prevent a release.

We should really start that API audit though.  These inconsistencies
don't make me super confident in the plugins. :(

On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
 wrote:
> Since I believe Lorin is away, I have tagged the release for blackberry.
>
> On 13-10-01 1:01 PM, "Marcel Kinard"  wrote:
>
>>If any platform owners don't have time to do this today, let me know how
>>I can help.
>>
>>On Oct 1, 2013, at 11:11 AM, Andrew Grieve  wrote:
>>
>>> I think all that needs
>>> to happen now is for all platform owners to update their JS snapshot
>>>again
>>> and push a "3.1.0" tag.
>>
>
> -
> This transmission (including any attachments) may contain confidential 
> information, privileged material (including material protected by the 
> solicitor-client or other applicable privileges), or constitute non-public 
> information. Any use of this information by anyone other than the intended 
> recipient is prohibited. If you have received this transmission in error, 
> please immediately reply to the sender and delete this information from your 
> system. Use, dissemination, distribution, or reproduction of this 
> transmission by unintended recipients is not authorized and may be unlawful.
>

Re: Mobilespec / CI / version problems

[David Kemp]

Just for clarification...

Testing 3.1.x works fine using 3.1 platforms, 3.1 mobilespec, and master
plugins.
Testing 'HEAD' works fine using master platforms, master mobilespec, and
dev plugins.

Thats all as expected.

Up until a week ago, you could test 3.0.x using 3.0.x platforms, 3.0.x
mobilespec, and master plugins.
That no longer works.



On Tue, Oct 1, 2013 at 12:40 PM, Joe Bowser  wrote:

> Aren't we testing 3.1.0 with the tests that were tagged in 3.1.0?
> Testing with 3.0.0 tests seems like you'll always have failing tests,
> since ideally the tests should have been added with the bug (although
> I don't know where to put platform-specific mobile-spec tests, the
> don't really have a home and people get upset when I check them in.)
>
>
>
> On Tue, Oct 1, 2013 at 9:34 AM, David Kemp  wrote:
> > I believe that will be OK - testing it out now.
> >
> > It still probably deserves some documentation somewhere that the
> previously
> > stated relationships don't work anymore, and that any plugin references
> in
> > a 3.0.x project need attention.
> >
> >
> >
> > On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve 
> wrote:
> >
> >> Would it fix it to use mobile-spec from master when testing 3.0.x?
> >> Mobile-spec generally stays in sync with the plugins more so than the
> >> platforms, so it would make sense to me to use mobile-spec at master if
> >> using plugins from master/dev.
> >>
> >>
> >> On Tue, Oct 1, 2013 at 4:40 PM, David Kemp  wrote:
> >>
> >> > The issue is the that stated methodology for getting the right
> versions
> >> to
> >> > test is:
> >> > * for release, get plugins from the master branch and platforms, tests
> >> etc
> >> > from the release branch (3.0.x)
> >> > * for tip of tree, get plugins from the dev branch and platforms,
> tests
> >> etc
> >> > from the master branch
> >> > Since the rename was done to the plugins on master (appropriate for
> >> 3.1.x)
> >> > that no longer leaves a place to get plugins that are 'compatible'
> with
> >> > 3.0.x
> >> >
> >> > The issue that I am pointing out right now is that the file:
> >> > cordova-mobile-spec/dependencies-plugin/plugin.xml
> >> > explicitly names the plugins with the old name in the 3.0.x branch of
> >> > mobile-spec. so it breaks.
> >> >
> >> > If a developer has a similar references to their 3.0.x plugins, it
> will
> >> > also fail next time they build a fresh new project.
> >> >
> >> > For CI it means that all tests of the 3.0.x branch now fail.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard 
> >> wrote:
> >> >
> >> > > In the past I've used #3. When checking out code to test, I try to
> get
> >> > all
> >> > > the assets from the same branch / time period. But I may be skewed
> in
> >> > that
> >> > > approach, since our product that embeds Cordova has a snapshot of
> the
> >> > > platforms and plugins, and doesn't get updates from the online
> repos.
> >> > >
> >> > > Does what you are saying infer that the rename of the plugins is a
> >> > > breaking change? And needs to have some verbage in the Upgrading
> >> guides?
> >> > >
> >> > > On Oct 1, 2013, at 11:14 AM, David Kemp 
> wrote:
> >> > >
> >> > > > Summary: Due to the renaming of plugins, there is no longer a
> >> sensible
> >> > > way
> >> > > > to test 3.0.x
> >> > > >
> >> > > > Detail:
> >> > > > The process to test 3.0.x is to get platforms, mobile-spec, etc
> from
> >> > > 3.0.x
> >> > > > and plugins from master. With the change on plugin names (remove
> >> core)
> >> > > the
> >> > > > 3.0.x mobile-spec still refers to the names with core , but the
> >> master
> >> > > > branch of the plugins no longer have that name.
> >> > > >
> >> > > > Possible resolutions:
> >> > > > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed
> in
> >> > 3.1.x
> >> > > > 2) cherrypick the change to mobilespec dependencies back to 3.0.x
> >> > > > 3) find some other way to get the older plugins available to test.
> >> > > >
> >> > > > Thoughts?
> >> > > >
> >> > > > David Kemp
> >> > >
> >> > >
> >> >
> >>
>

Re: Tagging 3.1.0 today?

[Jeffrey Heifetz]

Since I believe Lorin is away, I have tagged the release for blackberry.

On 13-10-01 1:01 PM, "Marcel Kinard"  wrote:

>If any platform owners don't have time to do this today, let me know how
>I can help.
>
>On Oct 1, 2013, at 11:11 AM, Andrew Grieve  wrote:
>
>> I think all that needs
>> to happen now is for all platform owners to update their JS snapshot
>>again
>> and push a "3.1.0" tag.
>

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

Re: Mobilespec / CI / version problems

[David Kemp]

In answer to Andrews response, there was a problem with 3.0.x where the
echo plugin was mostly removed, but the two source files CDVEcho.m,
CDVEcho.h were left in iOS core. When you build 3.0.x with the master
version (or 3.1.x) of Mobilespec and it includes the new Echo plugin, you
get duplicate symbols.

We could fix that by back-patching 3.0.x to remove the two source files
(should have no effect), then the current master Mobilespec would build
with 3.0.x




On Tue, Oct 1, 2013 at 12:40 PM, Joe Bowser  wrote:

> Aren't we testing 3.1.0 with the tests that were tagged in 3.1.0?
> Testing with 3.0.0 tests seems like you'll always have failing tests,
> since ideally the tests should have been added with the bug (although
> I don't know where to put platform-specific mobile-spec tests, the
> don't really have a home and people get upset when I check them in.)
>
>
>
> On Tue, Oct 1, 2013 at 9:34 AM, David Kemp  wrote:
> > I believe that will be OK - testing it out now.
> >
> > It still probably deserves some documentation somewhere that the
> previously
> > stated relationships don't work anymore, and that any plugin references
> in
> > a 3.0.x project need attention.
> >
> >
> >
> > On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve 
> wrote:
> >
> >> Would it fix it to use mobile-spec from master when testing 3.0.x?
> >> Mobile-spec generally stays in sync with the plugins more so than the
> >> platforms, so it would make sense to me to use mobile-spec at master if
> >> using plugins from master/dev.
> >>
> >>
> >> On Tue, Oct 1, 2013 at 4:40 PM, David Kemp  wrote:
> >>
> >> > The issue is the that stated methodology for getting the right
> versions
> >> to
> >> > test is:
> >> > * for release, get plugins from the master branch and platforms, tests
> >> etc
> >> > from the release branch (3.0.x)
> >> > * for tip of tree, get plugins from the dev branch and platforms,
> tests
> >> etc
> >> > from the master branch
> >> > Since the rename was done to the plugins on master (appropriate for
> >> 3.1.x)
> >> > that no longer leaves a place to get plugins that are 'compatible'
> with
> >> > 3.0.x
> >> >
> >> > The issue that I am pointing out right now is that the file:
> >> > cordova-mobile-spec/dependencies-plugin/plugin.xml
> >> > explicitly names the plugins with the old name in the 3.0.x branch of
> >> > mobile-spec. so it breaks.
> >> >
> >> > If a developer has a similar references to their 3.0.x plugins, it
> will
> >> > also fail next time they build a fresh new project.
> >> >
> >> > For CI it means that all tests of the 3.0.x branch now fail.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard 
> >> wrote:
> >> >
> >> > > In the past I've used #3. When checking out code to test, I try to
> get
> >> > all
> >> > > the assets from the same branch / time period. But I may be skewed
> in
> >> > that
> >> > > approach, since our product that embeds Cordova has a snapshot of
> the
> >> > > platforms and plugins, and doesn't get updates from the online
> repos.
> >> > >
> >> > > Does what you are saying infer that the rename of the plugins is a
> >> > > breaking change? And needs to have some verbage in the Upgrading
> >> guides?
> >> > >
> >> > > On Oct 1, 2013, at 11:14 AM, David Kemp 
> wrote:
> >> > >
> >> > > > Summary: Due to the renaming of plugins, there is no longer a
> >> sensible
> >> > > way
> >> > > > to test 3.0.x
> >> > > >
> >> > > > Detail:
> >> > > > The process to test 3.0.x is to get platforms, mobile-spec, etc
> from
> >> > > 3.0.x
> >> > > > and plugins from master. With the change on plugin names (remove
> >> core)
> >> > > the
> >> > > > 3.0.x mobile-spec still refers to the names with core , but the
> >> master
> >> > > > branch of the plugins no longer have that name.
> >> > > >
> >> > > > Possible resolutions:
> >> > > > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed
> in
> >> > 3.1.x
> >> > > > 2) cherrypick the change to mobilespec dependencies back to 3.0.x
> >> > > > 3) find some other way to get the older plugins available to test.
> >> > > >
> >> > > > Thoughts?
> >> > > >
> >> > > > David Kemp
> >> > >
> >> > >
> >> >
> >>
>

Re: Mobilespec / CI / version problems

[David Kemp]

I am running regression tests on 3.0.x as well as tests on the tip of tree.
I have not yet switched to running regression on 3.1.x since it isn't
actually released yet.

The problem is that suddenly the 3.0.x tests fail. This is mostly because
the plugins are not tied to a release, but mobilespec is.

Ideally, I would expect that I should be able to go back and check out the
'right' versions and retest any release. That is not true currently since
there is no 'right' versions to get.


On Tue, Oct 1, 2013 at 12:40 PM, Joe Bowser  wrote:

> Aren't we testing 3.1.0 with the tests that were tagged in 3.1.0?
> Testing with 3.0.0 tests seems like you'll always have failing tests,
> since ideally the tests should have been added with the bug (although
> I don't know where to put platform-specific mobile-spec tests, the
> don't really have a home and people get upset when I check them in.)
>
>
>
> On Tue, Oct 1, 2013 at 9:34 AM, David Kemp  wrote:
> > I believe that will be OK - testing it out now.
> >
> > It still probably deserves some documentation somewhere that the
> previously
> > stated relationships don't work anymore, and that any plugin references
> in
> > a 3.0.x project need attention.
> >
> >
> >
> > On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve 
> wrote:
> >
> >> Would it fix it to use mobile-spec from master when testing 3.0.x?
> >> Mobile-spec generally stays in sync with the plugins more so than the
> >> platforms, so it would make sense to me to use mobile-spec at master if
> >> using plugins from master/dev.
> >>
> >>
> >> On Tue, Oct 1, 2013 at 4:40 PM, David Kemp  wrote:
> >>
> >> > The issue is the that stated methodology for getting the right
> versions
> >> to
> >> > test is:
> >> > * for release, get plugins from the master branch and platforms, tests
> >> etc
> >> > from the release branch (3.0.x)
> >> > * for tip of tree, get plugins from the dev branch and platforms,
> tests
> >> etc
> >> > from the master branch
> >> > Since the rename was done to the plugins on master (appropriate for
> >> 3.1.x)
> >> > that no longer leaves a place to get plugins that are 'compatible'
> with
> >> > 3.0.x
> >> >
> >> > The issue that I am pointing out right now is that the file:
> >> > cordova-mobile-spec/dependencies-plugin/plugin.xml
> >> > explicitly names the plugins with the old name in the 3.0.x branch of
> >> > mobile-spec. so it breaks.
> >> >
> >> > If a developer has a similar references to their 3.0.x plugins, it
> will
> >> > also fail next time they build a fresh new project.
> >> >
> >> > For CI it means that all tests of the 3.0.x branch now fail.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard 
> >> wrote:
> >> >
> >> > > In the past I've used #3. When checking out code to test, I try to
> get
> >> > all
> >> > > the assets from the same branch / time period. But I may be skewed
> in
> >> > that
> >> > > approach, since our product that embeds Cordova has a snapshot of
> the
> >> > > platforms and plugins, and doesn't get updates from the online
> repos.
> >> > >
> >> > > Does what you are saying infer that the rename of the plugins is a
> >> > > breaking change? And needs to have some verbage in the Upgrading
> >> guides?
> >> > >
> >> > > On Oct 1, 2013, at 11:14 AM, David Kemp 
> wrote:
> >> > >
> >> > > > Summary: Due to the renaming of plugins, there is no longer a
> >> sensible
> >> > > way
> >> > > > to test 3.0.x
> >> > > >
> >> > > > Detail:
> >> > > > The process to test 3.0.x is to get platforms, mobile-spec, etc
> from
> >> > > 3.0.x
> >> > > > and plugins from master. With the change on plugin names (remove
> >> core)
> >> > > the
> >> > > > 3.0.x mobile-spec still refers to the names with core , but the
> >> master
> >> > > > branch of the plugins no longer have that name.
> >> > > >
> >> > > > Possible resolutions:
> >> > > > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed
> in
> >> > 3.1.x
> >> > > > 2) cherrypick the change to mobilespec dependencies back to 3.0.x
> >> > > > 3) find some other way to get the older plugins available to test.
> >> > > >
> >> > > > Thoughts?
> >> > > >
> >> > > > David Kemp
> >> > >
> >> > >
> >> >
> >>
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

If any platform owners don't have time to do this today, let me know how I can 
help.

On Oct 1, 2013, at 11:11 AM, Andrew Grieve  wrote:

> I think all that needs
> to happen now is for all platform owners to update their JS snapshot again
> and push a "3.1.0" tag.

Re: Hello Apache Team

[Andrew Grieve]

Great. You should close the pull requests and close the JIRA issue now.


On Tue, Oct 1, 2013 at 5:13 PM, Maxime LUCE  wrote:

> Hello,
>
> Just a question.
> I saw my pull request have been merged into cordova-plugin-transfer's dev
> branch.
> May I wait the merge of dev branch into master branch to close pull
> request on Github ?
> Same question about the issue in JIRA ?
>
> Thanks
>
> Cordialement.
> Maxime LUCE
> max...@touchit.fr
> 06 28 60 72 34
> http://touchit.fr
>
>
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: lundi 30 septembre 2013 23:15
> To: dev@cordova.apache.org
> Subject: Re: Hello Apache Team
>
> Welcome Maxime!
>
> Thanks, I have pulled in your pull request, however, you will have to sign
> the CLA if you want to make any bigger contributions to the project.
>
> https://github.com/apache/cordova-plugin-file-transfer/pull/5
>
> http://wiki.apache.org/cordova/ContributorWorkflow
>
> Cheers,
>   Jesse
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Sep 30, 2013 at 11:43 AM, Marcel Kinard 
> wrote:
>
> > Maxime, welcome!
> >
> > Please take a look at
> http://wiki.apache.org/cordova/ContributorWorkflowwhich describes the
> steps for a contributor.
> >
> > On Sep 30, 2013, at 1:21 PM, Maxime LUCE  wrote:
> >
> > > Hello Apache Team,
> > >
> > > I plan to contribute on the Apache Cordova (and more) project. I
> > > already
> > create a pull request on cordova-plugin-filetransfer for Windows 8.
> > > I targeted some other issues in plugins implementations.
> > > I also plan to help on the cordova-cli and plugman projects to allow
> > more and more platforms to work with the CLI.
> > >
> > > I work in HTML5 Touch software development, so I have a great
> > > experience
> > on many devices. I use frequently Apache Cordova in my projects so I
> > target and fix many issue in my projects.
> > > I think I'm ready to publish theses fix to the community, so I want
> > > to
> > officially enter the contributors community.
> > >
> > > You can find my projects and contributions on Github :
> > > https://github.com/SomaticIT
> > > https://github.com/spatools
> > > https://github.com/Touchit
> > >
> > > Thanks for your work,
> > > Cordially.
> > >
> > > [Touch it]
> > >
> > > Maxime LUCE
> > >
> > > [Facebook]
> > >
> > > [Twitter]
> > >
> > > max...@touchit.fr
> > > 06 28 60 72 34
> > > http://touchit.fr
> > >
> > >
> > >
> >
> >
>

Re: Mobilespec / CI / version problems

[Joe Bowser]

Aren't we testing 3.1.0 with the tests that were tagged in 3.1.0?
Testing with 3.0.0 tests seems like you'll always have failing tests,
since ideally the tests should have been added with the bug (although
I don't know where to put platform-specific mobile-spec tests, the
don't really have a home and people get upset when I check them in.)



On Tue, Oct 1, 2013 at 9:34 AM, David Kemp  wrote:
> I believe that will be OK - testing it out now.
>
> It still probably deserves some documentation somewhere that the previously
> stated relationships don't work anymore, and that any plugin references in
> a 3.0.x project need attention.
>
>
>
> On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve  wrote:
>
>> Would it fix it to use mobile-spec from master when testing 3.0.x?
>> Mobile-spec generally stays in sync with the plugins more so than the
>> platforms, so it would make sense to me to use mobile-spec at master if
>> using plugins from master/dev.
>>
>>
>> On Tue, Oct 1, 2013 at 4:40 PM, David Kemp  wrote:
>>
>> > The issue is the that stated methodology for getting the right versions
>> to
>> > test is:
>> > * for release, get plugins from the master branch and platforms, tests
>> etc
>> > from the release branch (3.0.x)
>> > * for tip of tree, get plugins from the dev branch and platforms, tests
>> etc
>> > from the master branch
>> > Since the rename was done to the plugins on master (appropriate for
>> 3.1.x)
>> > that no longer leaves a place to get plugins that are 'compatible' with
>> > 3.0.x
>> >
>> > The issue that I am pointing out right now is that the file:
>> > cordova-mobile-spec/dependencies-plugin/plugin.xml
>> > explicitly names the plugins with the old name in the 3.0.x branch of
>> > mobile-spec. so it breaks.
>> >
>> > If a developer has a similar references to their 3.0.x plugins, it will
>> > also fail next time they build a fresh new project.
>> >
>> > For CI it means that all tests of the 3.0.x branch now fail.
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard 
>> wrote:
>> >
>> > > In the past I've used #3. When checking out code to test, I try to get
>> > all
>> > > the assets from the same branch / time period. But I may be skewed in
>> > that
>> > > approach, since our product that embeds Cordova has a snapshot of the
>> > > platforms and plugins, and doesn't get updates from the online repos.
>> > >
>> > > Does what you are saying infer that the rename of the plugins is a
>> > > breaking change? And needs to have some verbage in the Upgrading
>> guides?
>> > >
>> > > On Oct 1, 2013, at 11:14 AM, David Kemp  wrote:
>> > >
>> > > > Summary: Due to the renaming of plugins, there is no longer a
>> sensible
>> > > way
>> > > > to test 3.0.x
>> > > >
>> > > > Detail:
>> > > > The process to test 3.0.x is to get platforms, mobile-spec, etc from
>> > > 3.0.x
>> > > > and plugins from master. With the change on plugin names (remove
>> core)
>> > > the
>> > > > 3.0.x mobile-spec still refers to the names with core , but the
>> master
>> > > > branch of the plugins no longer have that name.
>> > > >
>> > > > Possible resolutions:
>> > > > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed in
>> > 3.1.x
>> > > > 2) cherrypick the change to mobilespec dependencies back to 3.0.x
>> > > > 3) find some other way to get the older plugins available to test.
>> > > >
>> > > > Thoughts?
>> > > >
>> > > > David Kemp
>> > >
>> > >
>> >
>>

Re: Mobilespec / CI / version problems

[David Kemp]

I believe that will be OK - testing it out now.

It still probably deserves some documentation somewhere that the previously
stated relationships don't work anymore, and that any plugin references in
a 3.0.x project need attention.



On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve  wrote:

> Would it fix it to use mobile-spec from master when testing 3.0.x?
> Mobile-spec generally stays in sync with the plugins more so than the
> platforms, so it would make sense to me to use mobile-spec at master if
> using plugins from master/dev.
>
>
> On Tue, Oct 1, 2013 at 4:40 PM, David Kemp  wrote:
>
> > The issue is the that stated methodology for getting the right versions
> to
> > test is:
> > * for release, get plugins from the master branch and platforms, tests
> etc
> > from the release branch (3.0.x)
> > * for tip of tree, get plugins from the dev branch and platforms, tests
> etc
> > from the master branch
> > Since the rename was done to the plugins on master (appropriate for
> 3.1.x)
> > that no longer leaves a place to get plugins that are 'compatible' with
> > 3.0.x
> >
> > The issue that I am pointing out right now is that the file:
> > cordova-mobile-spec/dependencies-plugin/plugin.xml
> > explicitly names the plugins with the old name in the 3.0.x branch of
> > mobile-spec. so it breaks.
> >
> > If a developer has a similar references to their 3.0.x plugins, it will
> > also fail next time they build a fresh new project.
> >
> > For CI it means that all tests of the 3.0.x branch now fail.
> >
> >
> >
> >
> >
> > On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard 
> wrote:
> >
> > > In the past I've used #3. When checking out code to test, I try to get
> > all
> > > the assets from the same branch / time period. But I may be skewed in
> > that
> > > approach, since our product that embeds Cordova has a snapshot of the
> > > platforms and plugins, and doesn't get updates from the online repos.
> > >
> > > Does what you are saying infer that the rename of the plugins is a
> > > breaking change? And needs to have some verbage in the Upgrading
> guides?
> > >
> > > On Oct 1, 2013, at 11:14 AM, David Kemp  wrote:
> > >
> > > > Summary: Due to the renaming of plugins, there is no longer a
> sensible
> > > way
> > > > to test 3.0.x
> > > >
> > > > Detail:
> > > > The process to test 3.0.x is to get platforms, mobile-spec, etc from
> > > 3.0.x
> > > > and plugins from master. With the change on plugin names (remove
> core)
> > > the
> > > > 3.0.x mobile-spec still refers to the names with core , but the
> master
> > > > branch of the plugins no longer have that name.
> > > >
> > > > Possible resolutions:
> > > > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed in
> > 3.1.x
> > > > 2) cherrypick the change to mobilespec dependencies back to 3.0.x
> > > > 3) find some other way to get the older plugins available to test.
> > > >
> > > > Thoughts?
> > > >
> > > > David Kemp
> > >
> > >
> >
>

Re: Plugman Release

[Steven Gill]

Firefoxos is broken on master after the refactor. It works fine on the
cordova-3.1.x branch though.

I am testing jesse's pull requests for CLI + plugman today for
cordova-3.1.x branch. If they look good I will merge them in. We should
release CLI + Plugman at the same time as 3.1.0. The release should be
based off cordova-3.1.x branch and not master.
On Oct 1, 2013 7:41 AM, "Andrew Grieve"  wrote:

> Braden's out doing intern interviews yesterday & today, so it's unlikely
> he'll see this email until tomorrow if not Thursday.
>
> We could still do a tools release, but just don't update the platforms.js
> file to point at 3.1.0. That said, I think I saw Firefox was broken on
> HEAD? Think we'll want to fix that before doing so.
>
> In terms of testing the RC - as Steven said - using cordova@3.0.10 should
> do the trick
>
>
> On Tue, Oct 1, 2013 at 2:22 AM, Jesse  wrote:
>
> > I have an open pull request I would like someone else to look at. [1]
> > This addresses the issue that Carlos brought up during plugin remove [2]
> > It would be great if this could be part of the release, or at least the
> > commit cherry picked into it.
> >
> > Cheers,
> >   Jesse
> >
> >
> >
> > [1]
> > https://github.com/purplecabbage/cordova-plugman/pull/2
> > [2]
> > https://issues.apache.org/jira/browse/CB-4943
> >
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Mon, Sep 30, 2013 at 4:12 PM, Steven Gill 
> > wrote:
> >
> > > I believe Braden did the same type of release for plugman that he did
> for
> > > cordova cli. He updated both packages on npm but set the latest tag to
> > > point to the previous version until we were ready to do our full
> release.
> > >
> > > If you install the CLI RC
> > > sudo npm install -g cordova@3.0.10, you actually get version 0.12.0 of
> > > plugman as a dependency.
> > >
> > > I will wait for Braden to chime in. I figure the CLI and Plugman should
> > > both be released on the same day we release 3.1.0.
> > >
> > >
> > >
> > > On Mon, Sep 30, 2013 at 1:39 PM, David Kemp  wrote:
> > >
> > > > +1  to a plugman npm release.
> > > >
> > > > David Kemp
> > > >
> > > >
> > > >
> > > > On Mon, Sep 30, 2013 at 4:34 PM, Steven Gill  >
> > > > wrote:
> > > >
> > > > > Anyone see any issue with me doing a npm plugman release today?
> > Testing
> > > > the
> > > > > CLI RC is kind of weird when the plugman dependency is
> incompatible.
> > > > >
> > > > > -Steve
> > > > >
> > > >
> > >
> >
>

RE: Hello Apache Team

[Maxime LUCE]

Hello,

Just a question.
I saw my pull request have been merged into cordova-plugin-transfer's dev 
branch.
May I wait the merge of dev branch into master branch to close pull request on 
Github ?
Same question about the issue in JIRA ?

Thanks

Cordialement.
Maxime LUCE
max...@touchit.fr
06 28 60 72 34
http://touchit.fr


-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: lundi 30 septembre 2013 23:15
To: dev@cordova.apache.org
Subject: Re: Hello Apache Team

Welcome Maxime!

Thanks, I have pulled in your pull request, however, you will have to sign the 
CLA if you want to make any bigger contributions to the project.

https://github.com/apache/cordova-plugin-file-transfer/pull/5

http://wiki.apache.org/cordova/ContributorWorkflow

Cheers,
  Jesse

@purplecabbage
risingj.com


On Mon, Sep 30, 2013 at 11:43 AM, Marcel Kinard  wrote:

> Maxime, welcome!
>
> Please take a look at http://wiki.apache.org/cordova/ContributorWorkflowwhich 
> describes the steps for a contributor.
>
> On Sep 30, 2013, at 1:21 PM, Maxime LUCE  wrote:
>
> > Hello Apache Team,
> >
> > I plan to contribute on the Apache Cordova (and more) project. I 
> > already
> create a pull request on cordova-plugin-filetransfer for Windows 8.
> > I targeted some other issues in plugins implementations.
> > I also plan to help on the cordova-cli and plugman projects to allow
> more and more platforms to work with the CLI.
> >
> > I work in HTML5 Touch software development, so I have a great 
> > experience
> on many devices. I use frequently Apache Cordova in my projects so I 
> target and fix many issue in my projects.
> > I think I'm ready to publish theses fix to the community, so I want 
> > to
> officially enter the contributors community.
> >
> > You can find my projects and contributions on Github :
> > https://github.com/SomaticIT
> > https://github.com/spatools
> > https://github.com/Touchit
> >
> > Thanks for your work,
> > Cordially.
> >
> > [Touch it]
> >
> > Maxime LUCE
> >
> > [Facebook]
> >
> > [Twitter]
> >
> > max...@touchit.fr
> > 06 28 60 72 34
> > http://touchit.fr
> >
> >
> >
>
>

Re: Mobilespec / CI / version problems

[Andrew Grieve]

Would it fix it to use mobile-spec from master when testing 3.0.x?
Mobile-spec generally stays in sync with the plugins more so than the
platforms, so it would make sense to me to use mobile-spec at master if
using plugins from master/dev.


On Tue, Oct 1, 2013 at 4:40 PM, David Kemp  wrote:

> The issue is the that stated methodology for getting the right versions to
> test is:
> * for release, get plugins from the master branch and platforms, tests etc
> from the release branch (3.0.x)
> * for tip of tree, get plugins from the dev branch and platforms, tests etc
> from the master branch
> Since the rename was done to the plugins on master (appropriate for 3.1.x)
> that no longer leaves a place to get plugins that are 'compatible' with
> 3.0.x
>
> The issue that I am pointing out right now is that the file:
> cordova-mobile-spec/dependencies-plugin/plugin.xml
> explicitly names the plugins with the old name in the 3.0.x branch of
> mobile-spec. so it breaks.
>
> If a developer has a similar references to their 3.0.x plugins, it will
> also fail next time they build a fresh new project.
>
> For CI it means that all tests of the 3.0.x branch now fail.
>
>
>
>
>
> On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard  wrote:
>
> > In the past I've used #3. When checking out code to test, I try to get
> all
> > the assets from the same branch / time period. But I may be skewed in
> that
> > approach, since our product that embeds Cordova has a snapshot of the
> > platforms and plugins, and doesn't get updates from the online repos.
> >
> > Does what you are saying infer that the rename of the plugins is a
> > breaking change? And needs to have some verbage in the Upgrading guides?
> >
> > On Oct 1, 2013, at 11:14 AM, David Kemp  wrote:
> >
> > > Summary: Due to the renaming of plugins, there is no longer a sensible
> > way
> > > to test 3.0.x
> > >
> > > Detail:
> > > The process to test 3.0.x is to get platforms, mobile-spec, etc from
> > 3.0.x
> > > and plugins from master. With the change on plugin names (remove core)
> > the
> > > 3.0.x mobile-spec still refers to the names with core , but the master
> > > branch of the plugins no longer have that name.
> > >
> > > Possible resolutions:
> > > 1) never mind - mobilespec for 3.0.x is broken, it will be fixed in
> 3.1.x
> > > 2) cherrypick the change to mobilespec dependencies back to 3.0.x
> > > 3) find some other way to get the older plugins available to test.
> > >
> > > Thoughts?
> > >
> > > David Kemp
> >
> >
>

Re: Mobilespec / CI / version problems

[David Kemp]

The issue is the that stated methodology for getting the right versions to
test is:
* for release, get plugins from the master branch and platforms, tests etc
from the release branch (3.0.x)
* for tip of tree, get plugins from the dev branch and platforms, tests etc
from the master branch
Since the rename was done to the plugins on master (appropriate for 3.1.x)
that no longer leaves a place to get plugins that are 'compatible' with
3.0.x

The issue that I am pointing out right now is that the file:
cordova-mobile-spec/dependencies-plugin/plugin.xml
explicitly names the plugins with the old name in the 3.0.x branch of
mobile-spec. so it breaks.

If a developer has a similar references to their 3.0.x plugins, it will
also fail next time they build a fresh new project.

For CI it means that all tests of the 3.0.x branch now fail.





On Tue, Oct 1, 2013 at 11:23 AM, Marcel Kinard  wrote:

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

Re: Review Request 14356: Plugins Release draft blog post

[Marcel Kinard]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14356/#review26560
---

Ship it!


Where you say that a new plugin release is being performed, would it make sense 
to list which plugins are being updated and what the new versions are? Then 
users could easily compare that against what they currently have installed to 
verify if they have the new versions.

- Marcel Kinard


On Sept. 30, 2013, 9:30 p.m., Steven Gill wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14356/
> ---
> 
> (Updated Sept. 30, 2013, 9:30 p.m.)
> 
> 
> Review request for cordova.
> 
> 
> Repository: cordova-site
> 
> 
> Description
> ---
> 
> I think you have to download the diff. Having a tough time getting it to 
> upload properly. This is the blog post for plugins release. Blog post is at 
> the bottom of the diff. 
> 
> 
> Diffs
> -
> 
>   /public/artwork.html 1526343 
>   /public/blog/index.html 1526343 
>   /public/index.html 1526343 
>   /public/rss.xml 1526343 
> 
> Diff: https://reviews.apache.org/r/14356/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Steven Gill
> 
>

Re: Mobilespec / CI / version problems

[Marcel Kinard]

In the past I've used #3. When checking out code to test, I try to get all the 
assets from the same branch / time period. But I may be skewed in that 
approach, since our product that embeds Cordova has a snapshot of the platforms 
and plugins, and doesn't get updates from the online repos.

Does what you are saying infer that the rename of the plugins is a breaking 
change? And needs to have some verbage in the Upgrading guides?

On Oct 1, 2013, at 11:14 AM, David Kemp  wrote:

> Summary: Due to the renaming of plugins, there is no longer a sensible way
> to test 3.0.x
> 
> Detail:
> The process to test 3.0.x is to get platforms, mobile-spec, etc from 3.0.x
> and plugins from master. With the change on plugin names (remove core) the
> 3.0.x mobile-spec still refers to the names with core , but the master
> branch of the plugins no longer have that name.
> 
> Possible resolutions:
> 1) never mind - mobilespec for 3.0.x is broken, it will be fixed in 3.1.x
> 2) cherrypick the change to mobilespec dependencies back to 3.0.x
> 3) find some other way to get the older plugins available to test.
> 
> Thoughts?
> 
> David Kemp

Mobilespec / CI / version problems

[David Kemp]

Summary: Due to the renaming of plugins, there is no longer a sensible way
to test 3.0.x

Detail:
The process to test 3.0.x is to get platforms, mobile-spec, etc from 3.0.x
and plugins from master. With the change on plugin names (remove core) the
3.0.x mobile-spec still refers to the names with core , but the master
branch of the plugins no longer have that name.

Possible resolutions:
1) never mind - mobilespec for 3.0.x is broken, it will be fixed in 3.1.x
2) cherrypick the change to mobilespec dependencies back to 3.0.x
3) find some other way to get the older plugins available to test.

Thoughts?

David Kemp

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Okay, I've finally got time again to focus on this. I'm fine with skipping
an RC announcement this time around. I'm pretty confident that the current
state of 3.1 is better than 3.0 :).

Docs & upgrade guides look great! Thanks Marcel.

I've just tagged 3.1.0 for JS+MobileSpec+HelloWorld. I think all that needs
to happen now is for all platform owners to update their JS snapshot again
and push a "3.1.0" tag.

I'll work on a release announcement in the meantime for everyone to review.


On Tue, Oct 1, 2013 at 3:50 PM, Andrew Grieve  wrote:

> Thanks for pointing this out Peter - filed CB-4965.
>
>
> On Tue, Oct 1, 2013 at 6:46 AM, Smith, Peter 
> wrote:
>
>> Don't know if this is related to the 'leaking docs' scenario, but FYI
>> when we fetched the official 3.0 source zip download yesterday we saw
>> there are some inconsistencies between the doc files in the
>> cordova-docs.zip and in the plugin zips. For example, compare the
>> media.md file in cordova-docs.zip and in cordova-plugin-media.zip. Which
>> one is the "correct" one?
>>
>> Peter.
>>
>> -Original Message-
>> From: Marcel Kinard [mailto:cmarc...@gmail.com]
>> Sent: Tuesday, 1 October 2013 2:16 PM
>> To: dev@cordova.apache.org
>> Subject: Re: Tagging 3.1.0 today?
>>
>> I noticed that cordova-docs wasn't tagged or branched at the same time
>> the platforms were branched into 3.1.x for rc1. This seems to leave open
>> the possibility for docs from platforms/plugins master (post 3.1.0) to
>> leak into the 3.1.0 docs. I realize that cordova-docs won't get branched
>> because of its internal directory structure, but I'm wondering if in the
>> future it would be wise to go ahead and do the equivalent of running
>> "rake version[3.1.0]" at the time that the 3.1.x branch is created. Then
>> during the rc period, docs would behave just like platforms where
>> changes would need to be put on 2 branches [master and 3.1.x] / doc
>> versions [edge and 3.1.x].
>>
>> Thoughts?
>>
>> On Oct 1, 2013, at 12:05 AM, Marcel Kinard  wrote:
>>
>> > I believe the docs are now done.
>> >
>> > https://issues.apache.org/jira/browse/CB-4962
>> > https://issues.apache.org/jira/browse/CB-4963
>> >
>> > The only thing left to do is to change the pointer to use this new
>> version.
>> >
>> > On Sep 30, 2013, at 4:43 PM, Andrew Grieve 
>> wrote:
>> >
>> >> Marcel - one big thing that hasn't happened yet is docs.
>>
>>
>>
>

Re: Hello Apache Team

[Andrew Grieve]

Awesome! Looking forward to your help on the project!


On Tue, Oct 1, 2013 at 6:50 AM, Maxime LUCE  wrote:

> CLA already filled and sent to secret...@apache.org.
>
>
> Cordialement.
> Maxime LUCE
> max...@touchit.fr
> 06 28 60 72 34
> http://touchit.fr
>
>
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: lundi 30 septembre 2013 23:15
> To: dev@cordova.apache.org
> Subject: Re: Hello Apache Team
>
> Welcome Maxime!
>
> Thanks, I have pulled in your pull request, however, you will have to sign
> the CLA if you want to make any bigger contributions to the project.
>
> https://github.com/apache/cordova-plugin-file-transfer/pull/5
>
> http://wiki.apache.org/cordova/ContributorWorkflow
>
> Cheers,
>   Jesse
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Sep 30, 2013 at 11:43 AM, Marcel Kinard 
> wrote:
>
> > Maxime, welcome!
> >
> > Please take a look at
> http://wiki.apache.org/cordova/ContributorWorkflowwhich describes the
> steps for a contributor.
> >
> > On Sep 30, 2013, at 1:21 PM, Maxime LUCE  wrote:
> >
> > > Hello Apache Team,
> > >
> > > I plan to contribute on the Apache Cordova (and more) project. I
> > > already
> > create a pull request on cordova-plugin-filetransfer for Windows 8.
> > > I targeted some other issues in plugins implementations.
> > > I also plan to help on the cordova-cli and plugman projects to allow
> > more and more platforms to work with the CLI.
> > >
> > > I work in HTML5 Touch software development, so I have a great
> > > experience
> > on many devices. I use frequently Apache Cordova in my projects so I
> > target and fix many issue in my projects.
> > > I think I'm ready to publish theses fix to the community, so I want
> > > to
> > officially enter the contributors community.
> > >
> > > You can find my projects and contributions on Github :
> > > https://github.com/SomaticIT
> > > https://github.com/spatools
> > > https://github.com/Touchit
> > >
> > > Thanks for your work,
> > > Cordially.
> > >
> > > [Touch it]
> > >
> > > Maxime LUCE
> > >
> > > [Facebook]
> > >
> > > [Twitter]
> > >
> > > max...@touchit.fr
> > > 06 28 60 72 34
> > > http://touchit.fr
> > >
> > >
> > >
> >
> >
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Thanks for pointing this out Peter - filed CB-4965.


On Tue, Oct 1, 2013 at 6:46 AM, Smith, Peter wrote:

> Don't know if this is related to the 'leaking docs' scenario, but FYI
> when we fetched the official 3.0 source zip download yesterday we saw
> there are some inconsistencies between the doc files in the
> cordova-docs.zip and in the plugin zips. For example, compare the
> media.md file in cordova-docs.zip and in cordova-plugin-media.zip. Which
> one is the "correct" one?
>
> Peter.
>
> -Original Message-
> From: Marcel Kinard [mailto:cmarc...@gmail.com]
> Sent: Tuesday, 1 October 2013 2:16 PM
> To: dev@cordova.apache.org
> Subject: Re: Tagging 3.1.0 today?
>
> I noticed that cordova-docs wasn't tagged or branched at the same time
> the platforms were branched into 3.1.x for rc1. This seems to leave open
> the possibility for docs from platforms/plugins master (post 3.1.0) to
> leak into the 3.1.0 docs. I realize that cordova-docs won't get branched
> because of its internal directory structure, but I'm wondering if in the
> future it would be wise to go ahead and do the equivalent of running
> "rake version[3.1.0]" at the time that the 3.1.x branch is created. Then
> during the rc period, docs would behave just like platforms where
> changes would need to be put on 2 branches [master and 3.1.x] / doc
> versions [edge and 3.1.x].
>
> Thoughts?
>
> On Oct 1, 2013, at 12:05 AM, Marcel Kinard  wrote:
>
> > I believe the docs are now done.
> >
> > https://issues.apache.org/jira/browse/CB-4962
> > https://issues.apache.org/jira/browse/CB-4963
> >
> > The only thing left to do is to change the pointer to use this new
> version.
> >
> > On Sep 30, 2013, at 4:43 PM, Andrew Grieve 
> wrote:
> >
> >> Marcel - one big thing that hasn't happened yet is docs.
>
>
>

Re: Tagging 3.1.0 today?

[Andrew Grieve]

Tough call. I think there are pros/cons either way.


On Tue, Oct 1, 2013 at 5:16 AM, Marcel Kinard  wrote:

> I noticed that cordova-docs wasn't tagged or branched at the same time the
> platforms were branched into 3.1.x for rc1. This seems to leave open the
> possibility for docs from platforms/plugins master (post 3.1.0) to leak
> into the 3.1.0 docs. I realize that cordova-docs won't get branched because
> of its internal directory structure, but I'm wondering if in the future it
> would be wise to go ahead and do the equivalent of running "rake
> version[3.1.0]" at the time that the 3.1.x branch is created. Then during
> the rc period, docs would behave just like platforms where changes would
> need to be put on 2 branches [master and 3.1.x] / doc versions [edge and
> 3.1.x].
>
> Thoughts?
>
> On Oct 1, 2013, at 12:05 AM, Marcel Kinard  wrote:
>
> > I believe the docs are now done.
> >
> > https://issues.apache.org/jira/browse/CB-4962
> > https://issues.apache.org/jira/browse/CB-4963
> >
> > The only thing left to do is to change the pointer to use this new
> version.
> >
> > On Sep 30, 2013, at 4:43 PM, Andrew Grieve  wrote:
> >
> >> Marcel - one big thing that hasn't happened yet is docs.
>
>

Re: Plugman Release

[Andrew Grieve]

Braden's out doing intern interviews yesterday & today, so it's unlikely
he'll see this email until tomorrow if not Thursday.

We could still do a tools release, but just don't update the platforms.js
file to point at 3.1.0. That said, I think I saw Firefox was broken on
HEAD? Think we'll want to fix that before doing so.

In terms of testing the RC - as Steven said - using cordova@3.0.10 should
do the trick


On Tue, Oct 1, 2013 at 2:22 AM, Jesse  wrote:

> I have an open pull request I would like someone else to look at. [1]
> This addresses the issue that Carlos brought up during plugin remove [2]
> It would be great if this could be part of the release, or at least the
> commit cherry picked into it.
>
> Cheers,
>   Jesse
>
>
>
> [1]
> https://github.com/purplecabbage/cordova-plugman/pull/2
> [2]
> https://issues.apache.org/jira/browse/CB-4943
>
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Sep 30, 2013 at 4:12 PM, Steven Gill 
> wrote:
>
> > I believe Braden did the same type of release for plugman that he did for
> > cordova cli. He updated both packages on npm but set the latest tag to
> > point to the previous version until we were ready to do our full release.
> >
> > If you install the CLI RC
> > sudo npm install -g cordova@3.0.10, you actually get version 0.12.0 of
> > plugman as a dependency.
> >
> > I will wait for Braden to chime in. I figure the CLI and Plugman should
> > both be released on the same day we release 3.1.0.
> >
> >
> >
> > On Mon, Sep 30, 2013 at 1:39 PM, David Kemp  wrote:
> >
> > > +1  to a plugman npm release.
> > >
> > > David Kemp
> > >
> > >
> > >
> > > On Mon, Sep 30, 2013 at 4:34 PM, Steven Gill 
> > > wrote:
> > >
> > > > Anyone see any issue with me doing a npm plugman release today?
> Testing
> > > the
> > > > CLI RC is kind of weird when the plugman dependency is incompatible.
> > > >
> > > > -Steve
> > > >
> > >
> >
>

Re: Review Request 14356: Plugins Release draft blog post

[Andrew Grieve]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14356/#review26558
---

Ship it!


Looks good! Don't forget to run "rake build" before committing.

- Andrew Grieve


On Sept. 30, 2013, 9:30 p.m., Steven Gill wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14356/
> ---
> 
> (Updated Sept. 30, 2013, 9:30 p.m.)
> 
> 
> Review request for cordova.
> 
> 
> Repository: cordova-site
> 
> 
> Description
> ---
> 
> I think you have to download the diff. Having a tough time getting it to 
> upload properly. This is the blog post for plugins release. Blog post is at 
> the bottom of the diff. 
> 
> 
> Diffs
> -
> 
>   /public/artwork.html 1526343 
>   /public/blog/index.html 1526343 
>   /public/index.html 1526343 
>   /public/rss.xml 1526343 
> 
> Diff: https://reviews.apache.org/r/14356/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Steven Gill
> 
>

Re: Tagging 3.1.0 today?

[Marcel Kinard]

What else can I help with to get this thing out the door?

On Oct 1, 2013, at 12:05 AM, Marcel Kinard  wrote:

> I believe the docs are now done.