Here are people who have contributed to Woodstox development:
(version numbers in brackets indicate release in which the problem was fixed)

Tatu Saloranta, tatu.saloranta@iki.fi: Author

Christian Niles:
  * Pointed out the improvement to wstx.jar, that will set system properties
    necessary to automatically make Woodstox the default StAX implementation
    to use
    [0.8.3]

James Fogarty:
  * Found 3 bugs (getElementText() not working, incorrect index offset
    for non-ns getAttributeLocalName(), index-out-of-bounds when there
    were lots of attribute names whose hashes collide)
    [1.0]

James Strachan:
  * Found problems with stream writer; namespace repairing mode was not
    working as expected
    [1.0]

Stepan Koltsov:
  * Found problems with event reader: was setting peeked event to null, yet
    trying to de-reference it
    [1.0]

Mat Gessel:
  * Pointed out a problem with XMLStreamReader.nextTag() implementation;
    was not skipping comments and PIs
    [1.0]

Dan Diephouse:
  * Reported problems with QName construction (null prefix causes
    exception on some QName implementations)
    [1.0.1]
  * Reported [WSTX-9] (sr.getTextCharacters() problems)
    [2.0.3/2.7]
  * Pointed out code that could be used to resolve [WSTX-26].

Sven Köhler:
  * Reported the problem with blocking input streams, and behaviour of
    the UTF8 decoder Woodstox uses: this could cause "too early" blocking
    of readers, in cases where event(s) could be returned before needing
    to read more from underlying input stream.
    [1.0.4/1.7]
  * Reported a bug in stream writer; a call to writeEmptyElement() followed
    by a call to writeEndElement() ignored latter call.
    [1.0.5/1.8.2]

Casey Bowman:
  * Pointed out the (potential) problem with javax.xml.stream.Location;
    return values are ints, and may thus overflow for BIG documents.
    StAX2 extensions (XMLStreamLocation2) added to properly deal with
    the problem.
    [1.8]

Stefan Wachter:
  * Reported a problem with handling of large documents; was sometimes
    throwing an ArrayIndexOutOfBounds exception (mostly when dealing
    with gzipped streams).
    [1.0.3/1.8.1]

Eric Jain:
  * Reported a bug in default namespace handling; was reporting a bogus
    problem when declaring an explicit namespace before the default one
    on a start element
    [1.0.3/1.8.1]
  * Re-reported the problem with UTF-8 streams and array bounds (originally
    reported by Stefan Wachter), and provided unit test to reproduce it.
    [1.0.4/1.8.1]

Marius Raschip:
  * Reported a problem with handling of UTF-16 (and in general all non-UTF-8
    multi-byte encodings): wasn't handling xml declaration correctly.
    [1.0.5/1.8.2]

Olivier Potonniee:
  * Reported compilation problems (incorrect package name for one class,
    conflicting method name for LineSuppressWriter)
    [1.0.6/1.9]

Ron Yang:
  * Reported an intermittent problem caused by broken handling of SymbolTable
    sharing, and also pointed out a potential solution (had been fixed for
    2.0 branch earlier, but not for 1.0.x).
    [1.0.7]

Ulrich Callmeier:
  * Reported a bug with START_DOCUMENT handling of XMLStreamWriter
    implementation
    [1.0.7/2.0]
  * Reported a bug with the input factory: entity and dtd resolvers were
    not being properly passed to instances
    [1.0.7/2.0]
  * Report a bug with WriterBase, base class for all encoding writers
    (attribute, element text): an NPE was thrown when trying to output
    encoded characters.
    [2.0.1/2.5]
  * Reported a bug in DTD-handling; DTDs that had enumerated value "-"
    (or "--"), were throwing an exception.
    [2.0.1/2.5]

Peter Tauter:
  * Reported a bug with WriterBase; see the entry next to Ulrich for details.

Linus Ericson:
  * Reported bugs:
    * [WSTX-3]: WDTD.java was missing one double quote from output
      [2.0.2/2.6]
    * [WSTX-7] SimpleNsStreamWriter was stripping out attribute namespaces
      [2.0.3/2.7]
    * [WSTX-114]: Handling of ID attribute values broken, in non-namespace
      mode: last character was dropped.
      [3.2]

Patrick D'Cruze:
  * Reported [WSTX-8]; nextTag() followed by peek() at the start of a
    document did not work.
    [2.0.3/2.7]

Erik Smith:
  * Reported [WSTX-9] (sr.getTextCharacters() problems)
    [2.0.3/2.7]

Kevin Vargo:
  * Reported [WSTX-9] (sr.getTextCharacters() problems)
    [2.0.3/2.7]

Heinz Drews:
  * Reported [WSTX-10] (handling of 3-byte UTF-8 Byte Order Marker did
    not work properly when XMLStreamReader was constructed for a Reader)
    [2.0.3/2.7]
  * Reported [WSTX-19] (unnecessary default namespace declarations written
    in repairing mode)
    [2.0.4/2.8.1]

Wolfgang Hoschek:
  * Reported [WSTX-27] (incorrect handling of #FIXED attribute defaults)
    [2.0.4/2.8.1]
  * Reported [WTSX-59]: Stream writer tries to quote \r and \t in
    prolog and epilog.
  * Pointed out countless other bugs based on extensive Nux and Xom
    xml compatibility suites (and w3c compatibility suite as well).
  * Pointed out multiple optimization possibilities (both on reader and
    writer side), esp. via performance
    test suite Nux has: this helped performance tuning of 3.0 release
    significantly.
  * Reported [WSTX-65], [WSTX-66] and [WSTX-67], regarding event handling
    problems.
    [3.0]
  * Pointed out compilation problem on JDK 1.4 with SAX2 API
    [3.2]
  * Reported [WSTX-96]
    [3.2]

Bartlomiej Rymkowski:
  * Reported [WSTX-28] (broken handling of property
    (WstxInputProperties.P_CUSTOM_INTERNAL_ENTITIES)
    [2.0.5/2.8.2]

Arjen Poutsma:
  * Reported [WSTX-45] (WstxEventReader#peek() throwing EOF instead
    of returning null), pointed out fix.
    [2.0.6/2.9.2]

John Kristian:
  * Reported [WSTX-46]: Trying to write another root element produced an
    incorrect error message
    [2.0.6/2.9.2]

Steve Yost:
  * Reported a problem with setting P_VALIDATE_STRUCTURE
    [2.0.6]
  * Reported a problem with stream writer when trying to output
    non-wellformed (multiple root elements) content even when
    structural well-formedness checks are disabled.

Anli Shundi:
  * Reported [WTSX-58]: a problem with DOMWrappingReader throwing an NPE, when
    accessing attribute properties of an element with only ns declarations.
    [3.0.0]

Lucian Holland:
  * Reported a bug in handling of StartDocument event, peeking and
    XMLEventReader.nextTag().
    [3.0.0]
  * Reported a stax incompliancy wrt. XMLStreamReader.next() not throwing
    NoSuchElementException after END_DOCUMENT event.
    [3.0.1/3.1]

Matt Solnit:
  * Reported [WSTX-72]: Output streams/writers sometimes closed when they
    should not be.
    [3.0.1/3.1]

Michael Kay:
  * Reported [WSTX-69]: Incorrect types returned by XMLStreamReader, when
    notations/entities are requested.
    [3.0.1/3.1]
  * Reported [WSTX-70]: External parsed entity reference resolution was
    not functioning correctly, was using wrong path context.
    [3.2.0]
  * Reported [WSTX-71]: Use of unchecked exceptions sub-optimal, for cases
    where it would be possible to just defer throwing of checked ones

Vim de Rammelaere:
  * Reported [WSTX-77]: Bug in DTDValidator.validateAttribute() -- wrong
    arguments passed to StringUtil.matches()
    [3.0.1/3.1] 

Mickael Goujon:
  * Reported [WSTX-81], contributed a patch for it: Calculation of
    char/byte offsets was buggy.
    [3.0.2/3.1]

Christian Bering:
  * Reported [WSTX-82], contributed a patch for it: URL handling code
    had problems on Windows, when referring to files on network drives.
    [3.0.2/3.1]

Oleg Rudenko:
  * Reported [WSTX-83], contributed a patch for it: NPE in ElemAttrs
    for namespace URI checks.
    [3.0.2/3.1]

Pavol Vaskovic:
  * Reported [WSTX-87], and documented the problem (including a unit test)
    which allowed otherwise hard-to-track problem to be quite easily
    resolved. Problem was that event writer could produce non-wellformed
    output for medium/large-sized content, when using Latin1 encoding.
    [3.0.3/3.1]

Michael Haeusler:
  * Reported [WSTX-88], suggested fix; Latin1 output wasn't working
    correctly: some characters in range 0x80 - 0xFF were output both
    as is, and as character entities
    [3.0.3/3.1]

Frank Baxter:
  * Reported [WSTX-89], with sample document that exhibits the problem:
    line number information was not properly updated in
    some cases (boundary condition with Windows, \r\n, linefeeds)
    [3.1.1]
  * Reported [WSTX-97], with sample document and code to reproduce
    the problem: Character offsets (for XMLStreamReader.getLocation())
    were sometimes decremented
    [3.1.1]
  * Reported [WSTX-141], supplied test case demonstrate it:
    Copying of CDATA events using XMLEventWriter was producing
    garbled output.
    [3.2.4]

Davanum Srinivas:
  * Reported [WSTX-90], submitted a patch (used as the guideline for
    the changes): output writing efficiency could be improved by
    using System.arraycopy() instead of basic character copying.
    Can improve speed even for relatively short strings, it turns out.
    [3.2]
  * Reported [WSTX-91], submitted patch (regression caused by changes
    for [WSTX-90]); array index of bounds on stream writer.
    [3.2]

Werner Donné:
  * Reported [WSTX-102], submitted patch to fix it: WStartDocument
    constructor would NPE when building using DOM source.
    [3.0.3 / 3.1.1]

Michael Allman: 
  * [WSTX-103] Repairing writer had a bug that could result in wrong
    prefix being reported/output.
    [3.0.4 / 3.1.2 / 3.2]

Sami Dalouche:
  * Pointed out [WSTX-106], unhelpful XMLStreamException being thrown
    when trying to write illegal attribute value characters
    [3.2.1]

Daniel Kulp:
  * Pointed out [WSTX-108] (Maven pom missing info), helped resolve
   [3.2.1]
  * Reported [WSTX-113] (problems with DOMSource when DOM parsed in
    non-namespace mode)
   [3.2.1]

Abde Sassi:
  * Reported [WSTX-109], a bug in xml declaration handling in multi-doc
    mode.
   [3.2.1]

Erik Bergersjö:
  * Reported [WSTX-110], problems regarding Exception root cause setting.
   [3.2.1]

Santiago Pericas-Geertsen:
  * Pointed out [WSTX-111], Stax TCK non-compliancy, regarding filtered stream
    reader
   [3.2.1]

Wouter Cordewiner:
  * Pointed out [WSTX-122], helped in adding EBCDIC support.
   [3.2.2]
  * Pointed out [WSTX-138], confusing error msg for xml declaration /
    physical encoding inconsistency (EBCDIC vs UTF-x)
   [3.2.3]

Lukasz Wielek:
  * Reported [WSTX-132], NPE when event writer was passing null namespace
    URI
   [3.2.3]

Yoon-Je Choi:
  * Reported [WSTX-134]: DOMWrapperingReader.isWhiteSpace was using
    incorrect check, suggested fix.
   [3.2.3]
  * Reported [WSTX-135]: Repairing stream writer was associating namespace
    bindings with parent element, pointed out solution.
   [3.2.3]

Matt Gormley:
  * Reported [WSTX-143], bug in handling of DEL char in UTF8Reader,
    suggested fix, submitted unit test.
   [3.2.4]

Jim Ancona:
  * Reported [WSTX-146], contributed a unit test for verifying fix.
   [3.2.5]

David Citron:
  * Reported [WSTX-145]: DOMWrappingReader was not implementing coalescing
    mode.
   [3.2.7]

Martin Vanek:
  * Reported [WSTX-144]: Problem when trying to output namespace declaration
    using a DOMResult-backed writer.
   [3.2.6]

Eduardo Ribeiro Rodrigues
  * Reported [WSTX-153]: XMLReporter not getting called for non-fatal
    validation errors
    [3.2.6]
  * Reported [WSTX-155]: NPE after reporting missing #REQUIRED attribute
    [3.2.6]

Daniel Rodrigue:
  * Reported [WSTX-158], provided a test: XMLStreamReader.isWhiteSpace()
    returns potentially incorrect value when text segments starts with an
    entity
    (reported by Daniel R)
    [3.2.7]

Pawel Lipka
  * [WSTX-162] Name/namespace-URI interning not enabled for DOM-backed
    readers, getProperty() claims they are
    [3.2.7]

Arash Amiri:
  * [WSTX-174] Some old App servers have broken QName impl, are missing
    3-arg constructor.
    [3.2.8]

Ian Brandt:
  * [WSTX-165] Add property (WstxOutputProperties.P_AUTOMATIC_END_ELEMENTS)
    to allow enabling/disabling automatic addition of end elements
    when closing stream writer 
    [3.2.8]

Roger Wegmann:
  * [WSTX-188] Could get an ArrayIndexOutOfBounds exception for
    StartElement.getAttributeByName() under specific conditions
    [3.2.9]

Andreas Veithen:
  * Reported [WSTX-190], NPE with DTD validator, missing attribute.
    [3.2.9]
  * Reported [WSTX-202], suggested fix for it: BijectiveNsMap#findPrefixByUri
    doesn't handle masked namespace declarations correctly 
    [3.2.9]

Stéphane Claret:
  * Reported [WSTX-204] Custom entity resolver setting was not working with
    SAX API (due to JDK impl idiocy)
   [3.2.9]
 
