So to consolidate the list of known issues that should be addressed before
cutting an RC:
* CB-7375 Investigate breaking changes at file plugin
* Android manual plugin tests not run yet
* CB-7410 lots of breakages of the Android native tests
* CB-7416 Windows+plugins. source-file is not
Do any of these known issues block the release? Can we start the vote today as
Steve wanted despite these issues?
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent: Friday, August 29, 2014 9:10 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
So
[mailto:cmarc...@gmail.com]
Sent: Friday, August 29, 2014 9:10 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
So to consolidate the list of known issues that should be addressed before
cutting an RC:
* CB-7375 Investigate breaking changes at file plugin
* Android manual plugin
There are a few issues on iOS (CB-7423).
Thanks,
Edna Morales
From: Marcel Kinard cmarc...@gmail.com
To: dev@cordova.apache.org
Date: 08/29/2014 12:10 PM
Subject:Re: [Discuss] 3.6.0 Release
So to consolidate the list of known issues that should be addressed before
cutting
My assumption is that this would be a platforms / tools / plugins release.
That's why the testing we've been doing here has been using plugins master
instead of plugins latest.
Now that I look back at recent history, I see that platforms and tools were
released concurrently, but not plugins. I
We used to, in the 2.x days, because we had to.
One of the stated goals of the 3.x series of releases was to decouple
platforms and plugins, so that we had the freedom to release plugins
weekly, if needed (and not even as a whole set; just the ones which had
significant improvements,) and update
@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
So to consolidate the list of known issues that should be addressed before
cutting an RC:
* CB-7375 Investigate breaking changes at file plugin
* Android manual plugin tests not run yet
* CB-7410 lots of breakages of the Android native tests
* CB-7416
From: Marcel Kinardmailto:cmarc...@gmail.com
Sent: 8/29/2014 8:10 PM
To: dev@cordova.apache.orgmailto:dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
So to consolidate the list of known issues that should be addressed before
cutting an RC:
* CB-7375 Investigate breaking changes
From: Marcel Kinardmailto:cmarc...@gmail.com
Sent: 8/29/2014 8:10 PM
To: dev@cordova.apache.orgmailto:dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
So to consolidate the list of known issues that should be addressed before
cutting an RC:
* CB-7375 Investigate
@cordova.apache.orgmailto:dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
So to consolidate the list of known issues that should be addressed
before
cutting an RC:
* CB-7375 Investigate breaking changes at file plugin
* Android manual plugin tests not run yet
* CB-7410 lots of breakages
-file is not correctly processed
Thx,
Sergey
Sent from my Windows Phone
From: Marcel Kinardmailto:cmarc...@gmail.com
Sent: 8/29/2014 8:10 PM
To: dev@cordova.apache.orgmailto:dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I'm looking at the broken native tests on Android.
On Aug 29, 2014, at 3:39 PM, Steven Gill stevengil...@gmail.com wrote:
With Joe on Vacation, is anyone looking into tagging cordova-android? I
could do it if no one else wants to.
-Steve
Sounds good Marcel.
Update: Only Android platform is left to tag
On Fri, Aug 29, 2014 at 12:52 PM, Marcel Kinard cmarc...@gmail.com wrote:
I'm looking at the broken native tests on Android.
On Aug 29, 2014, at 3:39 PM, Steven Gill stevengil...@gmail.com wrote:
With Joe on Vacation, is
I've fixed enough of the native tests on Android to be comfortable with
counting the native tests as successful. All the issues have been in the tests
themselves, not the platform. So based on that, the failures in the native
tests are no longer blockers.
That said, I haven't been running the
Thanks for the update! No worries. I will run the tests now and tag if
everything looks good.
-Steve
On Fri, Aug 29, 2014 at 3:16 PM, Marcel Kinard cmarc...@gmail.com wrote:
I've fixed enough of the native tests on Android to be comfortable with
counting the native tests as successful. All
notes and polished other related things.
-Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, August 27, 2014 12:57 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
Hopefully this gets resolved soon. Seeing how it is a BB only issue
[mailto:stevengil...@gmail.com]
Sent: Wednesday, August 27, 2014 12:57 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
Hopefully this gets resolved soon. Seeing how it is a BB only issue, it won't
hinder other platforms from tagging.
On Tue, Aug 26, 2014 at 1:53 PM, Josh Soref jso
Removes unnecessary rules tracing which is also incorrectly handled by
PS
Thx!
Sergey
-Original Message-
From: purplecabbage [mailto:purplecabb...@gmail.com]
Sent: Wednesday, August 27, 2014 11:26 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
All tagged too.
I'll take
/cordova-cli/commit/68d0d9f17cd1228ecadae852522416526868
Thx!
Sergey
-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
Sent: Wednesday, August 27, 2014 11:57 AM
To: dev@cordova.apache.org
Subject: RE: [Discuss] 3.6.0 Release
Jesse, could you please also
: Wednesday, August 27, 2014 1:11 PM
To: dev@cordova.apache.org
Subject: RE: [Discuss] 3.6.0 Release
Pushed the following fix to CLI master which adds back missing reference to fs
(requires for Windows platform).
https://github.com/apache/cordova-cli/commit/6662888cffaab997a0f6daa7657d10962b23cf31
In the issue, @kamrik suggested a possible quick fix. Can we do that so that
releasing 3.6.0 is not blocked ?
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Wednesday, August 20, 2014 10:56 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
Parashuram Narasimhan wrote:
Wanted to ping about the 3.6.0 thread.
Are all the open issues taken care of?
No, the nice thing about issues is that you can check and see.
Is there something we can help on?
...
https://github.com
I'm running mobile-spec (plugins + non-plugins + automatic + manual +
platforms) with master on Android and finding a few failing tests, but they are
getting fixed. With an impending 3.6.0 release soon, I would assume many others
are doing the same. But perhaps that's not a good assumption.
On
We found a few issues with Windows Phone 8.1 (whitelist does not allow HTTP)
that Sergey discussed and is fixing.
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent: Tuesday, August 26, 2014 11:54 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
discussed and is fixing.
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent: Tuesday, August 26, 2014 11:54 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I'm running mobile-spec (plugins + non-plugins + automatic + manual +
platforms
with Windows Phone 8.1 (whitelist does not allow
HTTP) that Sergey discussed and is fixing.
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent: Tuesday, August 26, 2014 11:54 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I'm running mobile
Given that both the blockers are now closed, will we be starting a vote thread
next?
-Original Message-
From: Bryan Higgins [mailto:br...@bryanhiggins.net]
Sent: Tuesday, August 26, 2014 1:05 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
BB10 should be good to go
: [Discuss] 3.6.0 Release
BB10 should be good to go now.
I published cordova-blackberry10 as a package [1]. We had already updated
the name in package.json due to the strict name checking in CLI, so this
had to be done anyway.
Adding all packages to bundledDependencies works around the 'npm install
There's still a problem w/ blackberry10.
We have code that assumes the location of the blackberry10 code in
~/.cordova/lib/blackberry10,
https://issues.apache.org/jira/browse/CB-7409
I found this while working on the version script (which we should have
replaced a while ago…).
@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
BB10 should be good to go now.
I published cordova-blackberry10 as a package [1]. We had already updated
the name in package.json due to the strict name checking in CLI, so this
had to be done anyway.
Adding all packages to bundledDependencies
Hopefully this gets resolved soon. Seeing how it is a BB only issue, it
won't hinder other platforms from tagging.
On Tue, Aug 26, 2014 at 1:53 PM, Josh Soref jso...@blackberry.com wrote:
There's still a problem w/ blackberry10.
We have code that assumes the location of the blackberry10 code
Wanted to ping about the 3.6.0 thread. Are all the open issues taken care of?
Is there something we can help on?
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Tuesday, August 19, 2014 1:11 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
Parashuram Narasimhan wrote:
Wanted to ping about the 3.6.0 thread.
Are all the open issues taken care of?
No, the nice thing about issues is that you can check and see.
Is there something we can help on?
...
https://github.com/apache/cordova-lib/pull/75
Steven Gill wrote:
How does everyone feel about me starting the release process next Tuesday,
August 12, 2014?
Will your platform be ready?
My platform is definitely not ready, since apparently the npm by-default
stuff broke blackberry10.
I don't have the keys for the registry, and Bryan is on
Seems bb10 was just never published to npm. Josh want to take a stab at
this? Should be as simple checking out the tag and typing npm publish
On Tue, Aug 19, 2014 at 12:15 PM, Josh Soref jso...@blackberry.com wrote:
Steven Gill wrote:
How does everyone feel about me starting the release
I did publish it before.
https://www.npmjs.org/package/cordova-blackberry
On Tuesday, August 19, 2014, Andrew Grieve agri...@chromium.org wrote:
Seems bb10 was just never published to npm. Josh want to take a stab at
this? Should be as simple checking out the tag and typing npm publish
On
npm info cordova-blackberry10--- 404
npm info cordova-blackberry--- OK
cli is looking for blackberry10 as npm name but it's blckberry.
I think the altplatform: 'blackberry' in platforms.js can solve this.
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I think that A) is likely the feasible solution for 3.6.0.
B) seems like a 4.0-scope project (but an interesting one; I hadn't considered
it working in that direction) We'd probably spend a while debating the
particulars -- I don't know
: Re: [Discuss] 3.6.0 Release
I'll see about committing that today; I've had to reorganize it quite a
bit after the Big Config Refactor.
Joe, I'm pretty certain that your code is still in master, but definitely
add those tests to make sure, and to make sure we don't regress.
Ian
On Mon, Aug
@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I'll see about committing that today; I've had to reorganize it quite
a bit after the Big Config Refactor.
Joe, I'm pretty certain that your code is still in master, but
definitely add those tests to make sure, and to make sure we don't regress
...@google.com] On Behalf Of Ian
Clelland
Sent: Tuesday, August 12, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I've created CB-7291 for the whitelist issue, and I've ported the code
from June to the new-style configuration architecture and committed
, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I've created CB-7291 for the whitelist issue, and I've ported the code
from June to the new-style configuration architecture and committed it
to a
named CB-7291 branch on cordova-android.
If anyone has any
...@google.com [mailto:iclell...@google.com] On Behalf Of
Ian Clelland
Sent: Tuesday, August 12, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I've created CB-7291 for the whitelist issue, and I've ported the code
from June to the new-style configuration architecture
Sent: Tuesday, August 12, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I've created CB-7291 for the whitelist issue, and I've ported the code
from June to the new-style configuration architecture and committed it
to a
named CB-7291 branch
, August 12, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I've created CB-7291 for the whitelist issue, and I've ported the
code
from June to the new-style configuration architecture and committed
it
to a
named CB-7291 branch on cordova-android
Let's not release until the new whitelist is figured out. That feature is
too important. I also need to land the test to confirm my fix is still in
master.
Back from PTO tomorrow.
On Aug 11, 2014 6:55 AM, Mike Billau mike.bil...@gmail.com wrote:
There was talk about adding the internal
I agree with Joe.
On Aug 11, 2014, at 10:02 AM, Joe Bowser bows...@gmail.com wrote:
Let's not release until the new whitelist is figured out. That feature is
too important.
I'll see about committing that today; I've had to reorganize it quite a bit
after the Big Config Refactor.
Joe, I'm pretty certain that your code is still in master, but definitely
add those tests to make sure, and to make sure we don't regress.
Ian
On Mon, Aug 11, 2014 at 10:52 AM, Marcel
[mailto:iclell...@google.com] On Behalf Of Ian
Clelland
Sent: Monday, August 11, 2014 8:00 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release
I'll see about committing that today; I've had to reorganize it quite a bit
after the Big Config Refactor.
Joe, I'm pretty certain that your
49 matches
Mail list logo
