cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Higgins <bhigg...@blackberry.com>
Subject Re: BB10 and JIRA Etiquette
Date Thu, 04 Apr 2013 15:07:08 GMT
I think cataloguing the test failures for BB10 in JIRA is still a useful
exercise. Like Gord mentioned, our prototype will have close to the same
level support as the existing repo, but we plan to actively work on getting
close to 100% pass rate. Once we get our code public, I'll send an overview
out to the list for discussion. Ideally we'd like to contribute it all into
Apache.


On Thu, Apr 4, 2013 at 10:36 AM, Ken Wallis <kwallis@blackberry.com> wrote:

> Sorry for the hold up guys. The dev team is pushing hard to get those
> particular GitHub repos opened ASAP so we can openly discuss it, and get
> that code moved in. A couple more things to check off and we will be good
> to go.
>
> Thanks.
>
> Sent from my BlackBerry Z10 smartphone.
> From: Lorin Beer
> Sent: Thursday, April 4, 2013 7:02 AM
> To: dev
> Reply To: dev@cordova.apache.org
> Subject: Re: BB10 and JIRA Etiquette
>
>
> Yeah, I've heard rumours of the ull rewrite, but until they actually start
> showing their code and getting involved in the list discussion, I'm
> pretending like we should proceed with BB10 dev on our end as normal.
>
> Gord, any word on a timeframe for their involvement/contribution with
> Apache Cordova?
>
>
> On Thu, Apr 4, 2013 at 6:43 AM, Gord Tanner <gtanner@gmail.com> wrote:
>
> > 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 <lorin.beer.dev@gmail.com>
> > 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
> > >
> >
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message