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 7822EF81C for ; Wed, 8 May 2013 15:59:25 +0000 (UTC) Received: (qmail 15693 invoked by uid 500); 8 May 2013 15:59:25 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 15649 invoked by uid 500); 8 May 2013 15:59:25 -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 15640 invoked by uid 99); 8 May 2013 15:59:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 15:59:25 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of don.coleman@gmail.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 15:59:19 +0000 Received: by mail-ie0-f176.google.com with SMTP id at1so3400857iec.7 for ; Wed, 08 May 2013 08:58:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=69ec/sUBIpfUe3px8S38ejnuXGF5jYDMrXvpCX9+gcE=; b=JqVYTe0WcgKog0Z0U1jvzqAVj64QHIJ8nVN9z3y83J37Hdwuo2cHMRQn/lJcoeFAzz I2WuWwpyaAPv8RZ3Yq4dG7Ufp5OV5LqpWiQ8BMTbNhW9APtun6N0DcjpH7AEJHV9BFtj 2sQFrWPDHeywv4xtNOOW452wL+aRrwUfIN4nh5n3f9MM80kKKL/YF97pjmAbx03VHhvp qeuWMzrdKQ50lI/scG67YG6sAS3aWZX+Hqb1YiQ6oqIw+DrM8jgRymmWKIBb3ZBi92n2 lR/WpGVtS1sTTSKXAYwKCQu4IA1rLj7cAhMmXgeXDAqB+w0FWpz9uvOLsPk7Mj0eLRn6 8GaA== MIME-Version: 1.0 X-Received: by 10.50.178.172 with SMTP id cz12mr6077389igc.48.1368028738131; Wed, 08 May 2013 08:58:58 -0700 (PDT) Received: by 10.50.101.80 with HTTP; Wed, 8 May 2013 08:58:58 -0700 (PDT) In-Reply-To: References: Date: Wed, 8 May 2013 11:58:58 -0400 Message-ID: Subject: Re: Sending BB7 to the farm From: Don Coleman To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=089e0149c57efa9e9f04dc3702d7 X-Virus-Checked: Checked by ClamAV on apache.org --089e0149c57efa9e9f04dc3702d7 Content-Type: text/plain; charset=ISO-8859-1 I'd be happy to see BB7 go away. It seems like 3.0 could drop support, especially if BlackBerry is concentrating on 10 and not releasing webworks updates. I have a client asking for support BB7 along with Android and iOS. This probably means that I have a cordova-cli project and a separate BB7 build and keep BB7 on PhoneGap 2.x. On Wed, May 8, 2013 at 10:56 AM, Bryan Higgins wrote: > It is fair to say that our team is focused solely on BB10. The WebWorks SDK > for BBOS itself has no future planned releases. > > One point I should clear up is the new blackberry10 platform code we're > introducing does not cover PlayBook as well. The PlayBook runs TabletOS, > which while built on qnx does not as of yet have binary compatibility with > BB10. Our CEO has said BB10 for PlayBook is in development, but there have > been no official announcements regarding a release. > > > On Wed, May 8, 2013 at 10:27 AM, Lorin Beer >wrote: > > > Don's question regarding a BB7 roadmap yesterday made me realize that we > > don't have one. Concentrating on BB10/Playbook has caused us ignore BB7. > > > > A little while ago, BB7 was discussed in terms of sending her off to the > > farm/attic/(silicon afterlife). The decision was reached that we should > > keep up support. > > > > I believe BlackBerry's stance is that they are not interested in > > maintaining the BB7 Cordova implementation. Ken, Bryan, jump in here and > > correct me if I'm wrong. > > > > There is a lot of work involved in getting BB7 to the 3.0.0 cli stage, > and > > if the plan is to drop support for the platform entirely within the next > 6 > > months, I don't see that this work is justified. > > > > Deprecation policy is 3 releases now, which means 3.1.0 is the soonest we > > can drop it. > > > > Given that : > > - Brett on PhoneGap build has described the BB7 usage statistic as > "noise" > > - no new jira tickets are submitted for BB7 unless it's by our team > > > > I propose that we : > > > > 1. keep BB7 pre-cli maintenance mode regardless of how many releases it > > sticks around for > > > > 2. announce BB7 deprecation and drop BB7 before the 3.0.0 release > > > > The reasoning for 2 is to not pollute the 3.0 release with legacy code > > which is not CLI compliant. I realize that this contravenes our > deprecation > > policy, but I think the level of interest in BB7 may let us get away with > > it. > > > > - Lorin > > > --089e0149c57efa9e9f04dc3702d7--