Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of lorin.beer.dev@gmail.com
 designates 209.85.210.173 as permitted sender)
MIME-Version: 1.0
Date: Thu, 4 Apr 2013 06:10:45 -0700
Message-ID: 
 <CAASJe79z+8XOpZsp+Fu7wGv3gCiz+nYuUDpCz4v0Ceiev6LMfA@mail.gmail.com>
Subject: BB10 and JIRA Etiquette
From: Lorin Beer <lorin.beer.dev@gmail.com>
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7bdc0f0ece287104d988b2d7

--047d7bdc0f0ece287104d988b2d7
Content-Type: text/plain; charset=ISO-8859-1

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

--047d7bdc0f0ece287104d988b2d7--