On Tue, Feb 12, 2013 at 5:33 PM, James Teh <ja...@nvaccess.org> wrote: > Hi all, > > I'm one of the lead developers of NVDA. It is fantastic to see this work > progressing so well. It is something for which we (and our users) have been > hoping/waiting for years. I am very impressed with the progress so far. > > I eagerly await the decision regarding how issues should be reported and > would strongly urge for the bug tracker. Emails tend to get lost and are > much harder to triage or keep track of, especially for issues which won't be > addressed immediately. This is especially true on a high traffic, broad list > such as this one. Personally, I'm far likely to report bugs via a tracker, > as it means the time spent gathering information isn't wasted and I can > easily track the status of the issue and provide more info as needed. >
Using Bugzilla makes it easier for all of us. As Ariel suggested, if you enter the defect reports into Bugzilla, it would be good to preface the Subject line with [ia2] so it is clear that they are related to a branch build, not a trunk build. Also, if you (and anyone else testing in this area) can send me your Bugzilla account userid (the email address you registered with) I can add give you some additional permissions in Bugzilla, including ability to edit bugs, confirm, change status, etc. https://issues.apache.org/ooo/ Regards, -Rob > Thanks, > Jamie > > > On 10/02/2013 4:05 AM, V Stuart Foote wrote: >> >> Steve, >> >> Nothing substantive yet in working through the Windows build of the ia2 >> branch. Should we build against Linux and OSX and be testing for impact on >> ATK/AT-SPI and NSAccessibility User Interface? >> >> And, with QA and testing of the ia2 branch proceeding what mechanism >> should folks use for reporting and tracking issues on the ia2 branch builds? >> >> Should we stay with PM and ML exchanges, or start to use Bugzilla at >> issues.apache.org/ooo? I believe that starting with BZ tracking now >> provides continuity upon merge of branch back into AOO4.00. >> >> And, if into Bugzilla, would suggest a note in your AOO 4.0 IAccessible2 >> release planning wiki that QA participants and casual users report in >> Bugzilla categorized for consistency as against: >> >> Product: UI >> Component: AccessBridge >> Version: AOO4.00-dev >> >> Stuart >> >> =-=-= >> >> Sidebar--the legacy IAccessible2 enhancement bug could probably be revised >> https://issues.apache.org/ooo/show_bug.cgi?id=107914 >> >> And here is a generic BZ search for accessibility issues >> >> https://issues.apache.org/ooo/buglist.cgi?query_format=advanced&resolution=---&short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibility&short_desc_type=anywordssubstr&order=component%2Cpriority%2Cbug_severity&query_based_on= >> >> > > -- > James Teh > Director, NV Access Limited > Email: ja...@nvaccess.org > Web site: http://www.nvaccess.org/ > Phone: +61 7 5667 8372 >
