Nightly build #613 for cordova has succeeded!

[Apache Jenkins Server]

Nightly build #613 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g 
cordova@nightly'

For details check build console at 
https://builds.apache.org/job/cordova-nightly/613/consoleFull

-
Jenkins for Apache Cordova

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: FYI: Apache release process tools

[Shazron]

One thing OpenWhisk is doing is doing all this in a CI build to upload to
Apache SVN, versus our manual process.

https://github.com/apache/incubator-openwhisk-release

On Fri, Jan 26, 2018 at 8:58 AM, Shazron  wrote:

> While on the openwhisk-dev list, a thread there mentions some tools that
> may be of interest to us. Of course we are already using Apache RAT.
>
> -
> Apache Creadur includes three projects:
> - Apache Rat audits license headers. It will check if files have Apache
> License or not, and generate a report.
> - Apache Tentacles helps to audit in bulk components uploaded to a staging
> repository. It will check if there is a LICENSE and NOTICE files under each
> archived source package and compiled package. A HTML report will be
> generated.
> - Apache Whisker will generate a correct legal documentation if a package
> bundles code under several licenses.
> ---
>
> Apache Tentacles is kinda like our "coho check-license" but will not
> handle the package.json license field like our tool does.
> Apache Whisker is relevant since we do package non-Apache licensed code
> (but is Apache compatible)
>

FYI: Apache release process tools

[Shazron]

While on the openwhisk-dev list, a thread there mentions some tools that
may be of interest to us. Of course we are already using Apache RAT.

-
Apache Creadur includes three projects:
- Apache Rat audits license headers. It will check if files have Apache
License or not, and generate a report.
- Apache Tentacles helps to audit in bulk components uploaded to a staging
repository. It will check if there is a LICENSE and NOTICE files under each
archived source package and compiled package. A HTML report will be
generated.
- Apache Whisker will generate a correct legal documentation if a package
bundles code under several licenses.
---

Apache Tentacles is kinda like our "coho check-license" but will not handle
the package.json license field like our tool does.
Apache Whisker is relevant since we do package non-Apache licensed code
(but is Apache compatible)

Re: [DISCUSS] Cordova-Windows 6.0.0

[Jan Piotrowski]

The failures in https://github.com/apache/cordova-windows/pull/235 are
unrelated to that PR. Those are caused by the "Musts": If
https://github.com/apache/cordova-windows/pull/246 gets merged this
will be down to one, and the last one is
https://issues.apache.org/jira/browse/CB-13834

-J

2018-01-26 1:12 GMT+01:00 Jesse :
> Yeah, I agree that dumping 8.1 completely would be a lot of work, let move
> forward without that part.
>
> I think I agree with all your assessments!
>
> For the maybes:
> I think CB-13817  is less
> important, as it is something that even MS allows. They changed to call all
> UAP => UWP but they still have docs that say UAP.
> I would like to see https://github.com/apache/cordova-windows/pull/235 make
> it in, we'll need to look into the failures.
>
>
>
>
> @purplecabbage
> risingj.com
>
> On Thu, Jan 25, 2018 at 3:54 PM, Jan Piotrowski 
> wrote:
>
>> Hello.
>>
>> After we had to scrap release 5.1.0 because of an unexpected breaking
>> change (and broken CI and failing tests), I took the time to work a
>> bit on this and am now planning to go forward with a 6.0.0 release of
>> cordova-windows soonish.
>>
>> Current status:
>>
>> Must
>> - https://github.com/apache/cordova-windows/pull/246 (of
>> https://issues.apache.org/jira/browse/CB-13829) has to be reviewed and
>> merged
>> - https://issues.apache.org/jira/browse/CB-13834 has to be analyzed,
>> fixed, reviewed and merged
>>
>> Maybe
>> - https://issues.apache.org/jira/browse/CB-13817 could implement "UWP"
>> everywhere we currently use "UAP" (which will be kept as an alias)
>> - https://github.com/apache/cordova-windows/pull/235 should be
>> reviewed and merged as it is a nice new feature for Windows
>>
>> After
>> - Later https://github.com/apache/cordova-docs/pull/785 needs some
>> more work so docs at least partially match reality when 6.0.0 will be
>> released
>>
>> Am I missing anything?
>>
>> In the last release email Jesse suggested dropping 8.1 alltogether.
>> After spending some time with the code this would a) be super nice as
>> s much stuff could be deleted and removed but also b) pretty hard
>> as it is all connected and interwoven. Won't be quick to do.
>> More importantly I think we should use the release blog post to ask
>> cordova-windows users if 8.1 is still needed for them and how they are
>> using it in general so we get some input on how to proceed. (Some
>> feedback from Microsoft wouldn't be the worst idea either) If no one
>> uses it, we can do a clean 7.0.0 that removes it.
>>
>> Best,
>> Jan
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Cordova-Windows 6.0.0

[Jesse]

Yeah, I agree that dumping 8.1 completely would be a lot of work, let move
forward without that part.

I think I agree with all your assessments!

For the maybes:
I think CB-13817  is less
important, as it is something that even MS allows. They changed to call all
UAP => UWP but they still have docs that say UAP.
I would like to see https://github.com/apache/cordova-windows/pull/235 make
it in, we'll need to look into the failures.




@purplecabbage
risingj.com

On Thu, Jan 25, 2018 at 3:54 PM, Jan Piotrowski 
wrote:

> Hello.
>
> After we had to scrap release 5.1.0 because of an unexpected breaking
> change (and broken CI and failing tests), I took the time to work a
> bit on this and am now planning to go forward with a 6.0.0 release of
> cordova-windows soonish.
>
> Current status:
>
> Must
> - https://github.com/apache/cordova-windows/pull/246 (of
> https://issues.apache.org/jira/browse/CB-13829) has to be reviewed and
> merged
> - https://issues.apache.org/jira/browse/CB-13834 has to be analyzed,
> fixed, reviewed and merged
>
> Maybe
> - https://issues.apache.org/jira/browse/CB-13817 could implement "UWP"
> everywhere we currently use "UAP" (which will be kept as an alias)
> - https://github.com/apache/cordova-windows/pull/235 should be
> reviewed and merged as it is a nice new feature for Windows
>
> After
> - Later https://github.com/apache/cordova-docs/pull/785 needs some
> more work so docs at least partially match reality when 6.0.0 will be
> released
>
> Am I missing anything?
>
> In the last release email Jesse suggested dropping 8.1 alltogether.
> After spending some time with the code this would a) be super nice as
> s much stuff could be deleted and removed but also b) pretty hard
> as it is all connected and interwoven. Won't be quick to do.
> More importantly I think we should use the release blog post to ask
> cordova-windows users if 8.1 is still needed for them and how they are
> using it in general so we get some input on how to proceed. (Some
> feedback from Microsoft wouldn't be the worst idea either) If no one
> uses it, we can do a clean 7.0.0 that removes it.
>
> Best,
> Jan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

[DISCUSS] Cordova-Windows 6.0.0

[Jan Piotrowski]

Hello.

After we had to scrap release 5.1.0 because of an unexpected breaking
change (and broken CI and failing tests), I took the time to work a
bit on this and am now planning to go forward with a 6.0.0 release of
cordova-windows soonish.

Current status:

Must
- https://github.com/apache/cordova-windows/pull/246 (of
https://issues.apache.org/jira/browse/CB-13829) has to be reviewed and
merged
- https://issues.apache.org/jira/browse/CB-13834 has to be analyzed,
fixed, reviewed and merged

Maybe
- https://issues.apache.org/jira/browse/CB-13817 could implement "UWP"
everywhere we currently use "UAP" (which will be kept as an alias)
- https://github.com/apache/cordova-windows/pull/235 should be
reviewed and merged as it is a nice new feature for Windows

After
- Later https://github.com/apache/cordova-docs/pull/785 needs some
more work so docs at least partially match reality when 6.0.0 will be
released

Am I missing anything?

In the last release email Jesse suggested dropping 8.1 alltogether.
After spending some time with the code this would a) be super nice as
s much stuff could be deleted and removed but also b) pretty hard
as it is all connected and interwoven. Won't be quick to do.
More importantly I think we should use the release blog post to ask
cordova-windows users if 8.1 is still needed for them and how they are
using it in general so we get some input on how to proceed. (Some
feedback from Microsoft wouldn't be the worst idea either) If no one
uses it, we can do a clean 7.0.0 that removes it.

Best,
Jan

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Plugins Release

[Simon MacDonald]

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and subdependencies
have Apache-compatible licenses
* Ran mobilespec


Simon Mac Donald
http://simonmacdonald.com

On Thu, Jan 25, 2018 at 4:48 PM, Joe Bowser  wrote:

> I vote +1
> * Ran through manual tests of camera, splashscreen, inappbrowser
> * Ran mobilespec auto tests
>
> On Thu, Jan 25, 2018 at 11:59 AM, Suraj Pindoria  >
> wrote:
>
> > Please review and vote on the release of this plugins release
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-13826
> >
> > The plugins have been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/CB-13826/
> >
> > The packages were published from their corresponding git tags:
> > cordova-plugin-file-transfer: 1.7.1 (8747b4018e)
> > cordova-plugin-media: 5.0.2 (f90bac5f32)
> > cordova-plugin-camera: 4.0.2 (4b276ee534)
> > cordova-plugin-splashscreen: 5.0.2 (09e1f06fb0)
> > cordova-plugin-inappbrowser: 2.0.2 (7eb2e1ea03)
> >
> > Upon a successful vote I will upload the archives to dist/, upload them
> to
> > npm, and post the corresponding blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/
> release-voting.md
> > How to vote on a plugins release at
> > https://github.com/apache/cordova-coho/blob/master/docs/
> > plugins-release-process.md#voting
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and subdependencies
> > have Apache-compatible licenses
> > * Ran mobilespec
> >
>

Re: [VOTE] Plugins Release

[Joe Bowser]

I vote +1
* Ran through manual tests of camera, splashscreen, inappbrowser
* Ran mobilespec auto tests

On Thu, Jan 25, 2018 at 11:59 AM, Suraj Pindoria 
wrote:

> Please review and vote on the release of this plugins release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> Release issue: https://issues.apache.org/jira/browse/CB-13826
>
> The plugins have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-13826/
>
> The packages were published from their corresponding git tags:
> cordova-plugin-file-transfer: 1.7.1 (8747b4018e)
> cordova-plugin-media: 5.0.2 (f90bac5f32)
> cordova-plugin-camera: 4.0.2 (4b276ee534)
> cordova-plugin-splashscreen: 5.0.2 (09e1f06fb0)
> cordova-plugin-inappbrowser: 2.0.2 (7eb2e1ea03)
>
> Upon a successful vote I will upload the archives to dist/, upload them to
> npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> How to vote on a plugins release at
> https://github.com/apache/cordova-coho/blob/master/docs/
> plugins-release-process.md#voting
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> * Ran mobilespec
>

[VOTE] Plugins Release

[Suraj Pindoria]

Please review and vote on the release of this plugins release
by replying to this email (and keep discussion on the DISCUSS thread)

Release issue: https://issues.apache.org/jira/browse/CB-13826

The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-13826/

The packages were published from their corresponding git tags:
cordova-plugin-file-transfer: 1.7.1 (8747b4018e)
cordova-plugin-media: 5.0.2 (f90bac5f32)
cordova-plugin-camera: 4.0.2 (4b276ee534)
cordova-plugin-splashscreen: 5.0.2 (09e1f06fb0)
cordova-plugin-inappbrowser: 2.0.2 (7eb2e1ea03)

Upon a successful vote I will upload the archives to dist/, upload them to
npm, and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
How to vote on a plugins release at
https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and subdependencies
have Apache-compatible licenses
* Ran mobilespec