Is there any position for something like Release/Component Apprentice? :-)
Just in case a Master wants to train, delegate, have someone to cover for
vacation, or slap :-p, etc..
I will be interested to be apprentice since I'm getting started in the
community
--Carlos
On Tue, Jun 18, 2013 at
Ideally, all release steps are documented on the Wiki, and all progress
made during a release is reported in the release JIRA issues. So, I think
you'd get most of the way there by monitoring the issues commits read
the wiki. If there's anything you're in doubt about, then there's a good
chance
Hello everyone,
I have been working the last week on getting medic up and running here at
our office, and so far things are going pretty well. I would like to start
contributing our tests back to the community pretty soon. However, I
contacted Fil about flowing our test results back to the CI
Sounds great!
On Wed, Jun 19, 2013 at 9:39 AM, Mike Billau mike.bil...@gmail.com wrote:
Hello everyone,
I have been working the last week on getting medic up and running here at
our office, and so far things are going pretty well. I would like to start
contributing our tests back to the
I've been seeing similar issues with Jake since I've upgraded my node and
it is definitely related to Jake failing with dependencies. I have yet to
find the real root cause.
On 13-06-18 8:27 PM, Andrew Grieve agri...@chromium.org wrote:
As both Jesse and Shaz pointed out, I ran coho to update
This happened to me back when I upgraded node. I ended up doing rm -rf
node_modules and then npm install. I eventually managed to claw my way back
to a working Jake. Why it fails utterly silently, and with code 0, puzzles
me.
Braden
On Wed, Jun 19, 2013 at 12:00 PM, Jeffrey Heifetz
Any folks going to be at the //build conference in sf next week, hit me up and
lets grab a drink or 2.
mw
Sure thing. I'll use 2.9 as a dry run for me. FYI, I updated the broken links
in the checklist that were pointing to incubator.
-James Jong
On Jun 18, 2013, at 3:23 PM, Shazron shaz...@gmail.com wrote:
Thanks James!
Most of it is on the wiki, and is pretty straightforward:
Not
Great idea to expand the output.
I do prefer the explicit `ls` and would rather have the default be --help.
Given that, `ls` is harmless, so I don't much mind.
On Tue, Jun 18, 2013 at 1:36 PM, Michael Brooks mich...@michaelbrooks.cawrote:
I think [1] is up to the command patterns that
Would love to see this, thanks for taking the initiative on this Mike!
On 6/19/13 7:19 AM, Andrew Grieve agri...@chromium.org wrote:
Sounds great!
On Wed, Jun 19, 2013 at 9:39 AM, Mike Billau mike.bil...@gmail.com
wrote:
Hello everyone,
I have been working the last week on getting medic up
hmm, I did indeed just upgrade my node version. blowing away node_modules
didn't seem to fix it though.
On Wed, Jun 19, 2013 at 12:04 PM, Braden Shepherdson bra...@chromium.orgwrote:
This happened to me back when I upgraded node. I ended up doing rm -rf
node_modules and then npm install. I
I use nvm to switch back to node v0.8.14 when running jake on cordova-js.
Not a good solution.
On Wed, Jun 19, 2013 at 11:08 AM, Andrew Grieve agri...@chromium.orgwrote:
hmm, I did indeed just upgrade my node version. blowing away node_modules
didn't seem to fix it though.
On Wed, Jun 19,
One further piece of information for this Node version nonsense: 0.6 is too
old. 0.8 is too old, but only very thinly: we call os.tmpdir(), which
exists only in 0.10, renamed from os.tmpDir() in 0.8. os.tmpDir() still
exists as a synonym in 0.10 (though I don't think it appears in the
Hey guys,
There is no denying that the release branch practice is a little odd for
cordova-docs. This is because the cordova-docs repository versions
everything by directory (a legacy approach that we will someday shift away
from).
I'll hunt down the release wiki article and update it, but here
Makes sense. I'll cherry-pick my changes to the relevant branches.
On Wed, Jun 19, 2013 at 11:45 AM, Michael Brooks
mich...@michaelbrooks.cawrote:
Hey guys,
There is no denying that the release branch practice is a little odd for
cordova-docs. This is because the cordova-docs repository
Ahh shit I think we need to retag the JS
The dynamic loading of cordova_plugins.json doesn't work on Windows Phone
*, as we discussed in the 2.8.0rc1 tag thread. The workaround that Jesse
converged on has been sitting on a branch. You can compare it to apache's
master branch at [1]. Essentially
I'd like to reopen the topic of bundling node js into the blackberry
platform.
I have personally gotten feedback from users of errors which were caused by
node version inconsistencies. We have since updated the check_req script to
test for the minimum version of node we require, but that is not
Hm. This will of course require changing the name of the file Plugman
generates, and it will mean users need to be very careful to be using
sufficiently new plugman and cordova-js.
In short: only the upgrade path for users bothers me about this; the change
to use a .js file and script tag looks
Follow-up thought: No reason why we can't generate both cordova_plugins.js
and cordova_plugins.json for a while.
Braden
On Wed, Jun 19, 2013 at 3:06 PM, Braden Shepherdson bra...@chromium.orgwrote:
Hm. This will of course require changing the name of the file Plugman
generates, and it will
-1
I would rather we just use the system version of node which would be the
same version as the CLI. I can't think of any reason a specific platform
(aka BlackBerry) would need a special version of a common dependency.
Also I don't think you can bundle binaries in an apache release.
On Wed,
I was just going to suggest outputting both. That works for me.
@purplecabbage
risingj.com
On Wed, Jun 19, 2013 at 12:06 PM, Braden Shepherdson bra...@chromium.orgwrote:
Follow-up thought: No reason why we can't generate both cordova_plugins.js
and cordova_plugins.json for a while.
Braden
So for Cordova 3.0 in general, users will be required to pre-install a
minimum version of node globally?
We have had issues where upgrading node breaks stuff. I'd like to avoid
that and give users flexibility with their own system configuration.
On Wed, Jun 19, 2013 at 3:09 PM, Gord Tanner
I would expect they would have a supported node version when they type:
npm install cordova
which would do any version checks in the package.json [1] for supported
node versions
[1] -
https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blob_plain;f=package.json;hb=HEAD
On Wed, Jun 19,
For 3.0 will there still be a ZIP file released by Apache? Will the
instructions be download the latest version of node then run npm install
-g path to cordova-cli?
My assumption was the individual project templates will continue to work
independently of CLI.
Also, keep in mind that CLI invokes
The automated tests for Media frequently call new Media() with no URL,
which sends a null to the create action. In the past, this got turned
into the string null in Java, which was handled as a file named null
that didn't exist, and nothing crashed.
DataResource is fine with the files not
I'll make this change in plugman now.
On 6/19/13 12:10 PM, Jesse purplecabb...@gmail.com wrote:
I was just going to suggest outputting both. That works for me.
@purplecabbage
risingj.com
On Wed, Jun 19, 2013 at 12:06 PM, Braden Shepherdson
bra...@chromium.orgwrote:
Follow-up thought: No
Can we not have the script tag point to the json file? Does the extension
have to be .js?
On 6/19/13 12:10 PM, Jesse purplecabb...@gmail.com wrote:
I was just going to suggest outputting both. That works for me.
@purplecabbage
risingj.com
On Wed, Jun 19, 2013 at 12:06 PM, Braden Shepherdson
Still a -1, cordova (and all it's projects) should use the globally
installed version of node.
If someone needs multiple versions of node the should probably use nvm [1]
to manage it. IMHO this is a user problem and not something we should
magically solve via bundled copies of node or hardcoded
JSON files are not valid Javascript code.
On Wed, Jun 19, 2013 at 4:10 PM, Filip Maj f...@adobe.com wrote:
Can we not have the script tag point to the json file? Does the extension
have to be .js?
On 6/19/13 12:10 PM, Jesse purplecabb...@gmail.com wrote:
I was just going to suggest
Just pushed 0.7.12 of plugman that writes out both .js and .json files.
The .js file is wrapped in a cordova.define module whereas the .json file
is a simple array of plugins that were added using plugman.
Next I will update cordova-js to:
1. Try to load the .json file using an xhr
2. If that
Yeah, to Braden's point while it may work, the behavior is not guaranteed,
and could break later. Also the contents of the file differ between the 2
methods.
Also discussing this in a quick chat with Fil, I think the best approach is:
1. Plugman generates both files, a js and a json
2. cordova.js
I noticed in cordova-docs, the 2.8.0 tag was tagged in a commit on master,
but not in the 2.8.x branch. Furthermore, the commit that was tagged is not
even in the 2.8.x branch. Do I fix this?
On Wed, Jun 19, 2013 at 11:51 AM, Shazron shaz...@gmail.com wrote:
Makes sense. I'll cherry-pick my
Rhetorical question of course I am fixing this...
On Wed, Jun 19, 2013 at 1:36 PM, Shazron shaz...@gmail.com wrote:
I noticed in cordova-docs, the 2.8.0 tag was tagged in a commit on master,
but not in the 2.8.x branch. Furthermore, the commit that was tagged is not
even in the 2.8.x branch.
I've pushed a pl branch to cordova-js that combines both loading
techniques in the plugin_loader.
I am in the process of testing on android/ios/bb10. Benn is working on
testing that on the Windows Phone platforms.
If it all works out I will merge this back into master on cordova-js,
cherry pick
This commit that was tagged 2.8.0:
https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=1d2fdf5a3344a554136c505b162d1931e878daad
Does not occur in branch 2.8.x:
https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=shortlog;h=refs/heads/2.8.x
Nor does the tagged commit
Confirmed it works on android iOS and bb10.
Am gonna help Benn work through and make sure it's working on windows
phone *
On 6/19/13 1:24 PM, Jesse purplecabb...@gmail.com wrote:
Yeah, to Braden's point while it may work, the behavior is not guaranteed,
and could break later. Also the contents
I am testing on windows as well. I think I have a change, give me a few
minutes to verify.
@purplecabbage
risingj.com
On Wed, Jun 19, 2013 at 1:54 PM, Filip Maj f...@adobe.com wrote:
Confirmed it works on android iOS and bb10.
Am gonna help Benn work through and make sure it's working on
Benn and I just tested the pl branch of cordova-js on Windows Phone 7,
works well.
We are gonna test on WP8 now too.
On 6/19/13 2:03 PM, Jesse purplecabb...@gmail.com wrote:
I am testing on windows as well. I think I have a change, give me a few
minutes to verify.
@purplecabbage
risingj.com
Works on WP7 and Jesse reports it working on WP8.
I am merging back into master and retagging JS shortly.
On 6/19/13 2:03 PM, Jesse purplecabb...@gmail.com wrote:
I am testing on windows as well. I think I have a change, give me a few
minutes to verify.
@purplecabbage
risingj.com
On Wed,
Plugman and cordova-cli both require a minimum 0.9.9 node.
See the engines and engineStrict flags in package.json for the two
repos. engineStrict when set to true will force npm to make sure the
user's version of node adheres to what is listed under the engines prop.
On 6/19/13 1:15 PM, Gord
Ok so how do we update the JS on all platforms now? coho?
On Wed, Jun 19, 2013 at 2:19 PM, Filip Maj f...@adobe.com wrote:
Works on WP7 and Jesse reports it working on WP8.
I am merging back into master and retagging JS shortly.
On 6/19/13 2:03 PM, Jesse purplecabb...@gmail.com wrote:
I
Ha, my next question. I want to know too ...
I have pushed to master and cherry-pick'd into 2.9.x
My change just added support for a case where XHR was permitted, but there
wasn't a json file. It then attempts the script injection to load a .js
plugins file, instead of just giving up. This
Tag it the ol' fashioned way, then. Not sure why we need magic to do `git
tag 2.9.0rc1 git push --tags apache 2.9.x`
On 6/19/13 2:50 PM, Jesse purplecabb...@gmail.com wrote:
Ha, my next question. I want to know too ...
I have pushed to master and cherry-pick'd into 2.9.x
My change just added
Yeah I'm stalled on this one. If I run jake on cordova-js 2.9.x branch, the
version in the .js header is still 2.7.0 - checked the VERSION file is
correct.
On Wed, Jun 19, 2013 at 2:50 PM, Jesse purplecabb...@gmail.com wrote:
Ha, my next question. I want to know too ...
I have pushed to
Its the magical computeGitVersion in jakefile. Apparently it boils down:
$ git describe --tags --long
2.7.0rc1-94-g002f33d
Not sure why that returns 2.7.0, nor why we use that instead of VERSION.
I suggest moving forward and manually tagging.
On 6/19/13 2:52 PM, Shazron shaz...@gmail.com
Just re-tagged, test and fly!
I am now getting :
// Platform: windowsphone
// 2.9.0rc1-0-g002f33d
@purplecabbage
risingj.com
On Wed, Jun 19, 2013 at 2:52 PM, Shazron shaz...@gmail.com wrote:
Yeah I'm stalled on this one. If I run jake on cordova-js 2.9.x branch, the
version in the .js
Never mind me dum dum. Thanks Jesse
On Wed, Jun 19, 2013 at 2:52 PM, Shazron shaz...@gmail.com wrote:
Yeah I'm stalled on this one. If I run jake on cordova-js 2.9.x branch,
the version in the .js header is still 2.7.0 - checked the VERSION file is
correct.
On Wed, Jun 19, 2013 at 2:50
Ian, was this file supposed to be checked in?
https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=4c63589
https://issues.apache.org/jira/browse/CB-2840
Ran Apache RAT and noticed that one.
If you need a wav file for the beep, I have composed a CC licensed file
here:
https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;a=tree;f=common/resources;h=a9558f417570ee1793d34be30b81291750597153;hb=HEAD
@purplecabbage
risingj.com
On Wed, Jun 19, 2013 at 3:30 PM, Shazron
Looking at the issue, I don't think it needed a beep.wav, which makes me
think this was accidentally checked in
On Wed, Jun 19, 2013 at 4:00 PM, Jesse purplecabb...@gmail.com wrote:
If you need a wav file for the beep, I have composed a CC licensed file
here:
Late to the game here, but to re-tag JS:
./cordova-coho/coho tag-release --version 2.9.0rc1 -r js
To update JS snapshots in all repos, coho can't handle that yet. I think
I'll break updating of JS out into its own command so that we can address
this usecase.
On Wed, Jun 19, 2013 at 6:05 PM,
null could be interpreted as a relative URL I think. The current handling
of relative URLs by plugins is sadly plugin-specific.
On Wed, Jun 19, 2013 at 4:04 PM, Braden Shepherdson bra...@chromium.orgwrote:
The automated tests for Media frequently call new Media() with no URL,
which sends a
On Wed, Jun 19, 2013 at 7:41 PM, Andrew Grieve agri...@chromium.org wrote:
null could be interpreted as a relative URL I think. The current handling
of relative URLs by plugins is sadly plugin-specific.
Isn't that one of the things that DataResource is supposed to standardize?
The string
Okay, made more sense to just update the existing command to handle this.
For next time, we can just re-tag the JS and re-run:
./cordova-coho/coho prepare-release-branch --version 2.9.0rc1
and it will update all the JS snapshots on both master and the release
branch.
On Wed, Jun 19, 2013 at
Agree that we should make Media() an error, but we don't want to change the
semantics of relative URLs for APIs without proper deprecation.
On Thu, Jun 20, 2013 at 12:00 AM, Ian Clelland iclell...@google.com wrote:
On Wed, Jun 19, 2013 at 7:41 PM, Andrew Grieve agri...@chromium.org
wrote:
Thanks Shaz!
I was away for JSConf, so another contributor handled the cordova-docs
release for 2.8.0.
Michael
On Wed, Jun 19, 2013 at 1:46 PM, Shazron shaz...@gmail.com wrote:
This commit that was tagged 2.8.0:
56 matches
Mail list logo
