Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7F37F9CE for ; Thu, 4 Apr 2013 13:44:12 +0000 (UTC) Received: (qmail 28795 invoked by uid 500); 4 Apr 2013 13:44:12 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 28500 invoked by uid 500); 4 Apr 2013 13:44:11 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 28464 invoked by uid 99); 4 Apr 2013 13:44:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 13:44:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gtanner@gmail.com designates 74.125.82.177 as permitted sender) Received: from [74.125.82.177] (HELO mail-we0-f177.google.com) (74.125.82.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 13:44:03 +0000 Received: by mail-we0-f177.google.com with SMTP id o45so2033856wer.36 for ; Thu, 04 Apr 2013 06:43:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=CC5XTAPpTNVT3scgE64e48hp+2CdZG4u/Ccbx9ZhIKE=; b=OVmSREBP0xjx7Q6ZIC7uUxXOyKb7nCCVrlfhyEKYYXnF+8lKQapOGJDFlPeI1sJxIg 407me/AP7WM0z2aY36NC6R1pvp8rSrrDuNNHfqQxOArz80ipX7jfXrbbsUuGS2wZ/AQC ws4VqPLl1wyl6/13q/HSGYz0XWN8y51ZFpt/AXAgk3DoS8KriRRNwbdqMNyVOCx0GAqp 8J0xrOfzDpPNOot1fEg/+1No20a2f3qqaDQIrBWrX0xfmLfY4CR7B7nuzsNATJ4YG6TW xop0Y9pb+nKTQbZOYlpF1c0GjIQ2epf7F/y3SOvfuymP5d1hIHllREiPh0VpyKj3DRFM l1vQ== X-Received: by 10.180.188.3 with SMTP id fw3mr9347113wic.33.1365083022666; Thu, 04 Apr 2013 06:43:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.26.67 with HTTP; Thu, 4 Apr 2013 06:43:22 -0700 (PDT) In-Reply-To: References: From: Gord Tanner Date: Thu, 4 Apr 2013 06:43:22 -0700 Message-ID: Subject: Re: BB10 and JIRA Etiquette To: dev@cordova.apache.org Content-Type: multipart/alternative; boundary=001a11c37cdca7b24904d98928c8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c37cdca7b24904d98928c8 Content-Type: text/plain; charset=ISO-8859-1 The BlackBerry team has said on this list that they are rewriting everything for BlackBerry 10. They haven't shared any of the code yet but have warned that it is a complete rewrite. I am expecting it to be about the same support (or more). I think the issues are still valid as I can't imagine much changing when they rewrite everything. BlackBerry can chime in with more information. On Thu, Apr 4, 2013 at 6:10 AM, Lorin Beer wrote: > I've started cataloguing the failing tests and missing functionality on > BB10. > There's about 50 failing tests, and many more missing features (minor and > major). > > What I'm wondering is this: > 1. dump all the issues in jira as I find them > or > 2. report the issues as I get an opportunity to fix them > > given the number of failing tests and issues, it would be some months > before I could get around to fixing all of them. > > On one hand, we get these issues documented so users see were aware of it, > and can indicate what they need fixed, not to mention encouraging others to > take on some of these issues. > > On the other hand, it'll bloat our issue count. :) > > Wondering what the best approach is. > > - Lorin > --001a11c37cdca7b24904d98928c8--