Re: Sending BB7 to the farm

lation? Our 5% threshold may be hiding some of the story when we look only at a single global number. -- Marcel Kinard On May 9, 2013, at 4:32 PM, Filip Maj wrote: > +1 sunsetting BB7 > > On 5/8/13 8:58 AM, "Don Coleman" wrote: > >> I'd be happy to see BB7 go

AWOL

forward to helping out here again. -- Marcel Kinard

Re: Sending BB7 to the farm

tarted guides for iOS and Android are nice and clear on this topic. -- Marcel Kinard On May 13, 2013, at 4:41 PM, Lorin Beer wrote: > Absolutely Marcel, > > although, the impetus behind dropping BB is not the usage numbers, but the > lack of interest in future support beyond mai

standard slides?

your presentation slides, especially any that cite Cordova usage in apps? Thanks! -- Marcel Kinard

announcing 2.8.0 to apache.org homepage

ot be mentioned there? Looks like it is just a post to annou...@apache.org. Does anyone have experience with this? -- Marcel Kinard

Re: Baby Grieve

Congrats! My first one was 4 weeks early and about 5.5 lbs. Everything turned out fine. Slept alot during the first few weeks, then got noisy. Now she just completed her sophmore year in college, how time flies. -- Marcel Kinard On May 31, 2013, at 10:00 AM, Andrew Grieve wrote: > Comin

Re: announcing 2.8.0 to apache.org homepage

I added a bullet to the Announce section of CuttingReleases. -- Marcel Kinard On May 30, 2013, at 6:25 PM, Steven Gill wrote: > It is a great idea. I can send a short announcement once 2.8.0 is ready. > On May 30, 2013 6:03 PM, "Benn Mapes" wrote: > >> I haven

Widening the window (was: The Deprecation of Froyo)

will be loathing by the Android folks here since they are looking forward to ripping 2.2 ugliness out, but I need to ask this question. Thanks! -- Marcel Kinard On Apr 26, 2013, at 8:18 PM, Lorin Beer wrote: > - list warning +1 > - follow 3-release deprecation policy on this +1 > - Jo

Re: Widening the window (was: The Deprecation of Froyo)

of the day, users are still going to have to use 2 different versions of Cordova when targeting these older iOS versions. Keeping Froyo in Cordova isn't enough to make that go away. tl;dr: I'm withdrawing the request to keep Froyo. -- Marcel Kinard

Re: [jira] [Commented] (CB-3560) Use mirror system for downloads

Follow the links here: http://wiki.apache.org/cordova/UpdatingTheWebsite -- Marcel Kinard On Jun 9, 2013, at 7:42 PM, "Brian M Dube (JIRA)" wrote: > >[ > https://issues.apache.org/jira/browse/CB-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpan

Re: CRC32 checksum failed with Cordova 2.2.0

t; threshold for you? 1: http://stats.unity3d.com/mobile/os-ios.html 2: http://david-smith.org/iosversionstats/ Thanks! -- Marcel Kinard On Jun 11, 2013, at 3:39 AM, Andreas Sander wrote: > Hi, > due to the fact that Cordova 2.2.0 is the last iOS 4 supporting release, I > need to get Cordova

Re: Plugin and CordovaPlugin

-level pointer to it in cordova-docs so consumers know they should be monitoring it. And so they can go back months later and look at the history easily (i.e., why did my plugin break in 2.2?). Comments? -- Marcel Kinard

Re: [27/46] docs commit: amidst globalization api

very nice cleanup in the docs, including the new style guide. -- Marcel Kinard On Jun 12, 2013, at 1:51 PM, mwbro...@apache.org wrote: > amidst globalization api > > > Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo > Commit: http://git-wip-us.apache.org/repo

Re: We need better contributions from new people

ated test suite that gets a lot better at catching breakages / regressions. Yes, this takes time to do, but when mobile-spec is run, you've got confidence. -- Marcel Kinard

Fwd: [27/46] docs commit: amidst globalization api

Mike, how about adding a reference to STYLESHEET.md in README.md, so people looking at README.md see the great style guidelines you authored? Or perhaps even collapse STYLESHEET.md into README.md so it's all inline in the README. -- Marcel Kinard Begin forwarded message: > From: Marce

Re: We need better contributions from new people

On Jun 12, 2013, at 6:10 PM, Joe Bowser wrote: > The problem with this approach is that we shouldn't rely on just > mobile-spec for our testing... > > The fact is that on Android, if you're doing changes to the core, you > should be running the JUnit tests included with the project... Sounds g

Re: We need better contributions from new people

procedure on this topic. The reason I'm asking these questions is it sounds like they haven't been talked about at this level of detail before, otherwise I would be getting schooled right now. ;-) -- Marcel Kinard

proximity API

FYI. https://hacks.mozilla.org/2013/06/the-proximity-api/ W3C Working Draft – Proximity Events. "The API is about detecting how close the device is to any other physical object, by accessing the proximity sensor."

Re: [27/46] docs commit: amidst globalization api

our repo, that I'm aware of. This is the only thing I've been able to find: https://github.com/davebalmer/joDoc/wiki https://github.com/davebalmer/joDoc/blob/master/TOC.mdown @mwbrooks, any other hints? -- Marcel Kinard

Re: Plugin and CordovaPlugin

On Jun 17, 2013, at 10:54 AM, Andrew Grieve wrote: > Marcel - I like your idea of adding release notes / deprecation notices to > the docs. Perhaps this could be merged with the upgrade guides? I think that would work. I put my Cordova consumer hat on and ask the question "the changelog to low

Re: We need better contributions from new people

etc.) > > to: > > - When we say "run the test suites" this includes all automated and manual > tests in mobile-spec that might be affected by the change, and any > platform-specific unit tests (i.e., cordova-android/test, > cordova-ios/CordovaLibTests, etc.) > >

Re: Release Masters?

On Jun 18, 2013, at 5:07 AM, Brian LeRoux wrote: > Think we already have this as per the issue tracker concept of 'leads' > but I do agree formalizing the role a little more would help. Do all the components leads (as listed in Jira) want to be release masters for their components? If not, Jame

Re: Documentation update to previous version

On Jun 17, 2013, at 6:21 PM, Shazron wrote: > Should I bother? I know they will go in edge. There are a couple of issues: > https://issues.apache.org/jira/browse/CB-3753 > https://issues.apache.org/jira/browse/CB-3752 > > Basically it's weird since if I added it to the 2.8.0 folder, it's not in

Re: Android - Removing the .api namespace

Sounds like I missed something. What firm date? On Jun 24, 2013, at 2:04 PM, Joe Bowser wrote: > Unlike other releases, 3.0 is the only one with a firm date.

Re: Question about the git workflow when working on a branch

rial. So the 3.0.0 branch is essentially dead, commits for the 3.0.0 release are now happening on master. So if you have contributions you want to make for 3.0.0, just follow the contributor workflow instructions and work with master, as they assume. -- Marcel Kinard On Jun 30, 2013, at 11:0

Re: CDVLogger went away in master

Are there a scenarios where it would be good to not have Logger in an app, such as permissions, footprint, or just not needing any logging functionality? I'm having a tough time thinking of any, so I'd also say: +1 leaving Logger in core

Re: restructuring guide content in doc

I really like Shaz's idea. But a couple questions: 1) Is it out-of-scope of Mike's task? 2) Getting rid of the folders and using the branches would make it difficult to do overhauls like this since all branches in cordova-docs would need updates. So optimize out the duplication (one folder, man

Re: failing tests on master

I added "test the code" verbage to the ContributorWorkflow and CommitterWorkflow wiki pages, using the consensus that was reached a few weeks ago: http://markmail.org/thread/kpn7ut7cga2es5lx If I didn't capture something correctly, let me know or just edit the pages. On Jul 8, 2013, at 2:32 PM,

Fwd: svn commit: r1500938 - in /cordova/site/public/wiki-images: contributor-git.graphml contributor-git.png

FYI, I tweaked the png diagram of the repo flow on https://wiki.apache.org/cordova/ContributorWorkflow to closer match reality. Let me know if I capture anything incorrectly. Begin forwarded message: > From: marc...@apache.org > Subject: svn commit: r1500938 - in /cordova/site/public/wiki-image

Re: Errors following "WorkingWithThree" wiki

I updated the wiki page with this info, until this issue is corrected. On Jul 8, 2013, at 9:49 PM, Andrew Grieve wrote: > Yes! Most of us here have hit that exact problem, but I guess it hadn't > made it to the ML yet. > > It's because Android's version script reports the version by parsing it

Re: Android - Removing the .api namespace

I'm cool with that, as long as the import change is listed in the Upgrade guide. On Jul 8, 2013, at 3:50 PM, Andrew Grieve wrote: > Want to bring this up again. > > There was a bit of discussion on the bug: > https://issues.apache.org/jira/browse/CB-4038 > > I've already gone ahead with creati

XML schema for plugin.xml and config.xml?

Would it make sense to have an xsd (XML schema) file for plugin.xml and config.xml, so that folks could programatically validate their xml files against the schema with a tool like xmllint? I'd be happy to do that.

Re: XML schema for plugin.xml and config.xml?

On Jul 9, 2013, at 9:38 PM, Michal Mocny wrote: > Seriously though, if the schema is changing isn't that all the more reason > to support validation so devs can get early confirmation? That is exactly my thought. Updating the xsd is relatively easy, and it's just one file per schema. Handling a

Re: Android - Removing the .api namespace

Normally being very averse to changing pubic API's, I'm with Andrew and Ian on this. If we are going to be making breaking changes, especially if they are small, do them all at once. On Jul 9, 2013, at 11:06 PM, Joe Bowser wrote: > So far, we've asked plugin developers to migrate from the old-

Re: Cordova 2.9 missing on Apache Project Release website?

In svn it is infra/doap_Cordova.rdf. I updated the DOAP file, and I think it takes about 3 hours for the cron job to fire to regenerate the html. The commit is listed in CB-4146. On Jul 10, 2013, at 1:19 PM, Shazron wrote: > I think its a DOAP file update: > http://callback-dev.markmail.org/th

Re: tag 3.0.0rc1 on Monday the 15th

When will the Upgrade Guides (2.9 -> 3.0) be written? That content is currently not in cordova-docs.

Re: XML schema for plugin.xml and config.xml?

initial draft implementation is ready for feedback, description is in https://issues.apache.org/jira/browse/CB-4195 (just plugin schema now, not config schema yet). On Jul 10, 2013, at 12:15 PM, Marcel Kinard wrote: > On Jul 9, 2013, at 9:38 PM, Michal Mocny wrote: > >> Seriousl

PG Day / OSCON

I'll be in Portland for PG Day and OSCON, arriving Wed afternoon. Would be awesome to meet other folks. Ping me if you'd like to get together for beverages / meal / activity. -- Marcel Kinard

Re: thoughts on 4.0 cadence

On Jul 17, 2013, at 12:33 PM, Brian LeRoux wrote: > Wherein we treat 3.10 and 3.11 as actual hardening not 'one more > thing' hardening. This pushes our release to the fall which is > typically better for conference season. Essentially the same as we > have it today excepting that we acknowledge

Re: thoughts on 4.0 cadence

On Jul 17, 2013, at 7:52 PM, Marcel Kinard wrote: > Doing significant feature add and shakeout in 1 month feels a bit rushed. …when it is of similarly large magnitude as the CLI.

Re: docs.cordova.io

Michael, could you add a little more detail regarding this step to CuttingReleases (even if you are the only person who has the credentials to do it)? Thanks! On Jul 19, 2013, at 10:53 AM, Steven Gill wrote: > I think Michael Brooks is the only one who can do that right now. He will > have to

Re: Website work

I've got it almost ready to commit, if you want to procrastinate longer ;-) On Jul 25, 2013, at 10:35 AM, Steven Gill wrote: > Yeah I already assigned it to myself. I knew this day would come... > > > On Thu, Jul 25, 2013 at 6:23 AM, Andrew Grieve wrote: > >> Steve's the guilty one here I th

Re: Website work

Steve, take a look at it now and see what you think. The big src zip now goes through the mirror selection, while the asc/md5/sha still comes from apache.org. On Jul 25, 2013, at 11:43 AM, Steven Gill wrote: > It's all yours Marcel!

Re: Website work

I was thinking that also. Done. I removed the repeated Download button in the detail section, as it seemed weird for the same-looking button to have a different behavior (get the zip). I'd like the style in this section to look similar to couchdb.apache.org so it's not vanilla text, but I haven

Re: Wiki Updated

+1 on getting the plugin repos listed somewhere. I would have a slight preference for them to be on the cordova.apache.org front page, even though that would indeed be ugly, but it would also make them first-class citizens and available to contributors. We've got a bazillion repos, the web page

W3C Vibration API

FYI. http://www.w3.org/TR/2013/CR-vibration-20130723/ I added this to the RoadmapProjects API as a potential.

authoring docs

FYI: @msierra, I added a shout-out to your style guide from the ContributorWorkflow and CommitterWorkflow wiki pages. Begin forwarded message: > From: Apache Wiki > Subject: [Cordova Wiki] Update of "ContributorWorkflow" by MarcelKinard > Date: July 29, 2013 3:35:18 PM EDT > To: Apache Wiki >

Re: Plugin / Platform mismatch problems

That could be accomplished with XSLT. And XPath has basic query capability. James Jong and I have skills in those. On Jul 26, 2013, at 2:19 PM, Filip Maj wrote: > Ahh yeah. Some kind of at-publish-time conversion of certain plugin.xml > fields to json fields? > > On 7/26/13 10:27 AM, "Anis KAD

Re: Away

FYI, I will also be away starting this afternoon and will be back on Aug 26. Although I will look forward to being connected again, I don't look forward to the amount of email that will await me then. On Jul 29, 2013, at 5:10 PM, Shazron wrote: > Hi guys, > I'll be away from Aug 1st and back o

Re: Moving on

Fil, you're a prolific coder, insightful, and a nice guy to work with. You will be missed. Best wishes for ya!

Windows repo

I'm building a downstream distribution of Cordova. I noticed some unusual things about the Windows (desktop) content: 1) on apache.org, there is no zip snapshot of the cordova-windows src for 3.0.0, even though cordova-windows.git is listed as a platform repo in the coho script. 2) on git-wip-

Re: Windows repo

lease of Cordova for Windows 8. > I am just one dude, and I did not have time to break out all of the > plugins, and add the CLI functionality. > > Re: #3, yes, there was a regression, not sure from where. > > @purplecabbage > risingj.com > > > On Thu, Sep 5,

Re: plugman / cli verbose by default?

Perfect. I also prefer light output when using the CLI, given that this output is not likely to be input to another shell tool via a pipe. +1 On Sep 6, 2013, at 12:57 PM, Brian LeRoux wrote: > I think this is reasonable. So, default is 'light logging'. As a module it > is no logging. As an opt

Re: When to do "Official Apache Releases"

+1 to still do these for each cadence release. I'm in a somewhat unique situation where Cordova gets bundled as a downstream distribution into a vendor product. The vendor product uses the Cordova native platforms and core plugins that get embedded in the product, the product doesn't fetch any

Re: 3.1 Release

Will the plugin repos get tagged? If so, do they get tagged on every weekly cycle, or only when a cadence lines up with a weekly cycle, or both? I see that StepsForPluginRelease wiki say it will happen, and the most recent coho looks like it will do it, but I currently see only tags for 3.0.0 an

Re: Dropping iOS 5.0 support

Out of curiosity, what would be your back-of-the-napkin calculation on the cost per Cordova release to keep iOS 5 support?

Re: Proposal: Change JIRA to have bugs as "unassigned" by default

This sounds like a solution to workflow issue. But what is our workflow? So if I understand correctly, the proposal is that a new bug that is unassigned means it has not been triaged. What would Jira state be for the following: - triaged and nobody plans to work on it yet (low priority) - triage

Re: 3.1 Release

I'm confused about the date for 3.1.0 final release. These two posts don't match. On Sep 19, 2013, at 11:27 PM, Andrew Grieve wrote: > Next Thursday: > - If everything seems fine with RC1, release 3.1.0 final. > On Sep 10, 2013, at 3:20 PM, Andrew Grieve wrote: > Monday 16th - Create releas

Re: Hello Apache Team

Maxime, welcome! Please take a look at http://wiki.apache.org/cordova/ContributorWorkflow which 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

Re: Tagging 3.1.0 today?

I am anxious to get "3.1.0 final", as we are about to ship a product that embeds it. I was hoping to get 3.1.0 final about a week and a half ago, and I've watched it slip for various reasons. I see Jeff's commit to the js today, and I think Jesse has a couple merges he'd like to get in some plu

Re: Tagging 3.1.0 today?

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 happen

Re: Tagging 3.1.0 today?

ere 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/brows

Re: Tagging 3.1.0 today?

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.

Re: Mobilespec / CI / version problems

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

Re: Review Request 14356: Plugins Release draft blog post

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

Re: Tagging 3.1.0 today?

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: Tagging 3.1.0 today?

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?

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

Re: Tagging 3.1.0 today?

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 bet

Re: Tagging 3.1.0 today?

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?

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,

Re: Tagging 3.1.0 today?

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

Re: Translations

The other thing I mentioned in https://issues.apache.org/jira/browse/CB-4964 is that (upon trivial inspection) it appears that the translations sitting in the edge dir actually are translations of 3.0, not 3.1. - should those translations be published as 3.0 docs? (I'm tempted to say yes) - is

Re: Tagging 3.1.0 today?

Andrew, before you did this, I was looking at it and also seeing something strange. Joe did a commit (6f17e9f), and it was tagged as 3.1.0, but it didn't appear to be on the 3.1.x branch, or at least the HEAD of the 3.1.x branch was behind where it should have been. When I did a "git checkout 3

Re: PSA: watch for stipped [CB-####] from patch subject line when using git am

It's that bracket-wrapping that drives the automatic comment insertion in the Jira item upon a git commit-push. http://www.apache.org/dev/svngit2jira.html On Oct 2, 2013, at 2:40 PM, Andrew Grieve wrote: > Crazy. Maybe we should just change our convention to not add []s around the > bug IDs? >

Re: PSA: watch for stipped [CB-####] from patch subject line when using git am

On second thought, it looks like the configured trigger is "CB-\d+", in which case the brackets don't matter. On Oct 2, 2013, at 2:45 PM, Marcel Kinard wrote: > It's that bracket-wrapping that drives the automatic comment insertion in the > Jira item up

Re: PSA: watch for stipped [CB-####] from patch subject line when using git am

So new format should be: CB-1234 Fixed the RockOn widget Correct?

Re: PSA: watch for stipped [CB-####] from patch subject line when using git am

using strings instead of JSON • e.g.: CB-1234 all: Fixed plugin loading paths that start with /. Should that verbage stay in? I don't think we do that consistently. On Oct 2, 2013, at 3:29 PM, Andrew Grieve wrote: > +1 > > > On Wed, Oct 2, 2013 at 8:17 PM, Marcel Kinar

Re: Tagging 3.1.0 today?

This is a great team. Thanks for all your efforts!

Re: PSA: watch for stipped [CB-####] from patch subject line when using git am

Ah, thanks for the clarification. I added some verbage to ContributorWorkflow to match. On Oct 2, 2013, at 9:35 PM, Andrew Grieve wrote: > That applies to cordova-js only, and I think it's a nice-to-have.

Re: Cordova versioning

Jan, if you are distributing a copy of Cordova in NetBeans, it would be nice for you to add yourself to the list of "Downstream distributions" at https://wiki.apache.org/cordova/FrontPage. Same for any distributors. On Oct 3, 2013, at 11:18 AM, Jan Becicka wrote: > Hi, > I'm a NetBeans develo

Re: CLI tool - Medic testing

repo README.md, cordova-docs, wiki/WorkingWithThree, … these should be cross-linked, and scoped to avoid duplication. On Oct 3, 2013, at 11:08 AM, Carlos Santana wrote: > Even better, I prefer things like this to be closer to the source/repo

Re: Tag 2.9.1

This thread seems to have gone quiet without a consensus. Should there be additional 2.9.x releases going forward? If so, how often? What kind of fixes should be backported? Include updated docs? On Oct 1, 2013, at 2:50 PM, Jesse wrote: > As soon as we are done with 3.1.0 it would be a good ti

pull request for win8

Jesse, while Carlos is out on vacation, could I ask you to put the following pull request on your to-do list? https://github.com/apache/cordova-js/pull/50 Thanks!

Re: Cordova for Ubuntu

Good question. I just added a couple paragraphs to the top of http://wiki.apache.org/cordova/BecomingACommitter Please feel free to edit my explanation and improve it. On Oct 7, 2013, at 1:52 PM, Brian LeRoux wrote: > Committer can commit. A contributor can send a pull request. The > differen

Re: buildbot failure in Cordova Testing on IOS_Master

This is awesome! Finding a breakage on a very narrow environment or a recent commit is exactly the kind of discovery I'm hoping for with buildbot/medic. I am really looking forward to getting buildbot/medic exposed to the whole team, and consolidating devices into it. David K / Mike B, keep up t

Re: [CB-3747] - We need a test video

I might be able to create something new here. What sizes and formats are needed? Would something short in duration work best, or does it need to be longer than ~15 seconds? On Oct 10, 2013, at 9:06 PM, Shazron wrote: > Added https://issues.apache.org/jira/browse/CB-5053

Fwd: (CB-2234) add "about" command to CLI

ch for just "Luke", looking at the form i > submitted, the public name field is just "Luke" > >> add "about" command to CLI >> -- >> >>Key: CB-2234 >>URL: https://issu

Re: officially supported plugins from the Cordova community

Here's the question I'm wondering about: The console plugin is not documented in cordova-docs. Is that an oversight, or is it a plugin that is treated differently? My take is that it is an oversight. If not, then what is the reasoning?

Jira admin

Could one of the folks with Jira karma add "3.1.0" to the list of released versions? Thanks!

Re: third-party cordova plugin registry

I don't see this workflow documented anywhere, or am I missing it? On Oct 15, 2013, at 9:56 PM, Anis KADRI wrote: > I agree that they should be encouraged. > > configuration is stored in plugman (even for cordova-cli) and one can > easily set a registry with `plugman config set registry > http:

Re: Tag 2.9.1

rplecabbage >>>>>> risingj.com >>>>>> >>>>>> >>>>>> On Mon, Oct 7, 2013 at 12:58 PM, Jesse MacFadyen < >>>>> purplecabb...@gmail.com >>>>>>> wrote: >>>>>> >>>>

Re: API changes between 2.9.x and 3.x

+1 On Oct 16, 2013, at 3:08 PM, Joe Bowser wrote: > I'm thinking that we don't want to move things > like API changes back, since this could complicate the release, which > should just be about stability fixes.

Re: CommitterWorkflow

The recent thread on the "Native Platform dev vs Web Project dev" workflows seems to have some application here. If the Apache Way is to distribute source (not saying it is a frequent way, but should be a supported way), then there isn't much documentation on how to get it up and running as Josh

Re: Intro Jerome

Jerome, if you haven't seen it already, here is a good place to start: http://wiki.apache.org/cordova/ContributorWorkflow On Oct 19, 2013, at 3:06 PM, Jerome Schmaltz wrote: > Hi! > > My name is Jerome and it's my first experience as a committer for Apache. > > I've been programming since 11

Re: 2.9.1 + 3.2.0rc1

BTW, I also found a couple failures in the Android native tests on 4.2.2 on a Nexus 7 with 3.2.0-rc1: junit.framework.AssertionFailedError at org.apache.cordova.test.BackButtonMultiPageTest.testViaHref(BackButtonMultiPageTest.java:63) junit.framework.ComparisonFailure: expected: but was

jira permissions

Could one of the Jira admins grant Jira karma to Josh? Thanks! Begin forwarded message: > From: "Josh Soref (JIRA)" > Subject: [jira] [Commented] (CB-5307) Remove references to Callback and > Incubator > Date: November 7, 2013 10:03:24 AM EST > To: iss...@cordova.apache.org > Reply-To: dev@cord

Re: Tools release today?

What is the trigger for doing a plugman release? As needed per bugs/features, or should it be at the same time as cli? I'd suggest the latter, since cli has either a pseudo-dependency or real dependency (depending on how you look at it) on plugman. On Nov 8, 2013, at 12:07 PM, Steven Gill wrot

Re: source repository info in plugin spec?

https://issues.apache.org/jira/browse/CB-5128 On Nov 8, 2013, at 12:29 PM, Don Coleman wrote: > I'm glad we have a plugin repo , but it doesn't > provide a lot of info about plugins. > > Can we consider adding a "source repository" tag to plugin.xml to help > people

Re: Tools release today?

I was reminded of http://wiki.apache.org/cordova/VersioningAndReleaseStrategy which says it is weekly, with cli and plugman together. Works for me. On Nov 8, 2013, at 12:18 PM, Marcel Kinard wrote: > What is the trigger for doing a plugman release? As needed per bugs/features, > or sho

  1   2   3   4   5   6   >