Do you all know about this?
http://ci.apache.org/builders/aoo-w7ia2/
We now have an automatic build of the ia2 branch running nightly. (and
successfully)
It is not loading up install bits for some reason, but I'll look at that
and fix it.
If you want to see the status of the latest build look for "Windows ia2
Branch" on this page:
http://ci.apache.org/projects/openoffice/
that page links to the build logs
<http://ci.apache.org/projects/openoffice/buildlogs/w7ia2/log/wntmsci12.pro.build.html>
and the buildbot log <http://ci.apache.org/builders/aoo-w7ia2/builds/6>,
and should have the latest build of the install packages.
Andrew
On 2/9/2013 10: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=
