Nightly build #849 for cordova has succeeded!

2018-09-13 Thread Apache Jenkins Server
Nightly build #849 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/849/consoleFull - Jenkins for Apache Cordova

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

2018-09-13 Thread Shazron
What Julio said -- broad strokes only. Julio -- if we have those numbers, we could add them. Unless it's an automatic process, it won't be reliable. On Thu, Sep 13, 2018 at 7:35 PM julio cesar sanchez wrote: > > I don't think that information is relevant for the report, as what we > usually

Re: Commit package-lock.json in next major Cordova release or not?

2018-09-13 Thread Chris Brody
I would like to voice a couple more concerns about this idea, despite the fact that we had already reached agreement and I have started participating in this task [1] (). My apologies for such bad timing. My major concern is that npm does not seem to be

Re: [DISCUSS] Update dependencies for nightly builds in master

2018-09-13 Thread Chris Brody
If I would try the following command in master branch of cordova-common (just an experiment): npm install cordova-common@^3.0.0-nightly I would see the following change in package.json: "dependencies": { -"cordova-common": "^2.2.0", +"cordova-common":

Re: [DISCUSS] Update dependencies for nightly builds in master

2018-09-13 Thread Oliver Salzburg
To my understanding, any suffixed version is never matched by a range. They have to be targeted explicitly. This can be easily observed at https://semver.npmjs.com/ by entering no range or * On 2018-09-13 12:53, Chris Brody wrote: I would really favor the idea of publishing -rc suffixed

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

2018-09-13 Thread julio cesar sanchez
I don't think that information is relevant for the report, as what we usually include are releases and information about them, so it's something we should mention when we release the master changes, not before. As the report talks about JIRA issues and we moved to github issues, should we add the

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

2018-09-13 Thread Chris Brody
There was a lot of work done on master branch for next major release in areas such as performance improvements, internal API cleanup, migtation away from shelljs, major test improvements that seem to be missing. On Thu, Sep 13, 2018, 12:14 AM Shazron wrote: > Please review and comment > >

Re: [DISCUSS] Update dependencies for nightly builds in master

2018-09-13 Thread Chris Brody
I would really favor the idea of publishing -rc suffixed versions to resolve the dilemma discussed here. I would favor starting with something like -rc.01 which could gracefully handle up to 99 rc versions. Assuming that -rc suffixed versions should be considered stable enough for master then

Re: [DISCUSS] Update dependencies for nightly builds in master

2018-09-13 Thread Oliver Salzburg
Alright, as long as we're talking about a manual process to resolve this conflict temporarily, I see it as a valid suggestion. However, I would still prefer if a -rc.0 suffixed version was published and then depended upon, for clarity. On 2018-09-13 11:49, Jan Piotrowski wrote: Chris didn't

Re: [DISCUSS] Update dependencies for nightly builds in master

2018-09-13 Thread Jan Piotrowski
Chris didn't really mention the actual problem he tried to solve with this PR in his initial email, and half the discussion here was about something totally different. My understanding of what he did was that he tried to find a way to test a new version of corova-create that requires new versions

Re: [DISCUSS] Update dependencies for nightly builds in master

2018-09-13 Thread Oliver Salzburg
On 2018-09-13 00:34, Chris Brody wrote: In case of major version bump each Cordova package will continue to keep dependency on previous patch release of other packages until we make the new release. Reading this makes me think I didn't understand an important part of the discussion. Isn't