Mailing-List: contact commits-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@cordova.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Wed, 13 Mar 2013 23:18:51 -0000
Message-ID: <20130313231851.6009.87464@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCordova_Wiki=5D_Update_of_=22ReportingBugs=22_by_FilMaj?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cordova Wiki" for c=
hange notification.

The "ReportingBugs" page has been changed by FilMaj:
http://wiki.apache.org/cordova/ReportingBugs?action=3Ddiff&rev1=3D5&rev2=3D6

Comment:
Added details on creating top-level issues with subtasks

- Users who file issues with us are a very important part in keeping this p=
roject alive and relevant, so thank you!
+ =3D Filing an issue on JIRA =3D
  =

- We use [[https://issues.apache.org/jira/browse/CB|JIRA]] to capture and s=
chedule bugs and tasks for Apache Cordova. We ask the reporter please ensur=
e they provide as much detail as possible. This includes:
+ We use [[https://issues.apache.org/jira/browse/CB|JIRA]] to track bugs, a=
nd thus you will need an account with [[https://issues.apache.org/jira/brow=
se/CB|JIRA]]!
  =

+ Cordova has as a goal to be relevant on mobile platforms, and thus we pri=
oritize bugs that are reproducible on real devices over emulators. If you a=
re filing an issue that is device-specific, please provide as much informat=
ion about the hardware as possible!
-   * operating system (including version)
-   * device and manufacturer
-   * any logs files
-   * expected behaviour vs actual result
- =

- Providing a reproducible test case would be great, if you can.
- =

- You will need an account with Apache JIRA.
  =

  When you go to Create an Issue, you will be presented with a dialog with =
a bunch of forms. The important ones to fill out are:
  =

@@ -25, +18 @@

   * Environment: if you have any additional details about your machine's e=
nvironment (OS, version, etc.), please provide it here.
   * Description: be as in-depth as you need to be. If you are unsure if yo=
u should provide code, you probably should provide code. Remember, any comm=
itter or contributor tackling your issue needs to a) reproduce the problem,=
 b) write a test for it, c) write a patch, and d) check that the test passe=
s. The more information you can provide, the better. If you want to take it=
 to a next level, provide a test, screenshots, or any other additional info=
rmation that can make going through a), b), c) and d) easier.
  =

+ =3D Filing an API Addition or New Feature =3D
+ =

+ The spirit of the Cordova project is platform-agnostic. As such, when int=
roducing new features, it is important to consider all platforms that are p=
art of the Cordova family. Understandably, not all contributors have the ti=
me, resources or equipment to effectively test and implement new features a=
cross the several+ platforms Cordova supports. The middle ground, then, is =
to keep track of which features have landed in which platforms. The Cordova=
 project does so via the issue tracker. JIRA allows for filing issues with =
sub-issues. Thus, to track a complex feature such as this, file a top-level=
 issue and create sub-tasks for:
+ =

+  * Documentation
+  * Test(s) (mobile-spec)
+  * cordova-cli integration, if applicable
+  * All platforms related to the issue (try to include as many as possible=
), with the core ones being:
+   * Android
+   * BlackBerry (10)
+   * iOS
+   * FirefoxOS
+   * Windows Phone 7
+   * Windows Phone 8
+   * Windows 8
+   * Optionally, "less" mainstream platforms such as Bada, Tizen, QT, and =
webOS.
+=20