<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright (C) 2004 The Apache Software Foundation. All rights reserved. -->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "../../dtd/document-v11.dtd">

<document>
    <header>
        <title>Jakarta POI - Patch Queue</title>
        <authors>
            <person email="greenrd@hotmail.com" name="Robin Green"/>
            <person email="barozzi@nicolaken.com" name="Nicola Ken Barozzi"/>
        </authors>
    </header>
    <body>
        <section>
            <title>Introduction</title>
            <p>
                This is an
                <strong>informal</strong> list - in chronological order -
                of some of the noteworthy patches that have been posted
                to the
                <code>developers</code> mailing list.
                These patches are not (yet) part of the POI project, but need reviewing for possible
                inclusion. This system was instituted because, due to the large volume of mail and
                the lack of time of the committers, some patches tended to get forgotten about. This
                queue does not guarantee that any patch will be reviewed within a reasonable time frame,
                but it does at least make them easier to find!
            </p>
            <p>
                <strong>Reviewers wanted!</strong> - If you have time to review and/or test these patches,
                we would be grateful for your time. Please post comments to the dev mailing lists.
            </p>
            <p>
                Before submitting a patch, please read the page on
                <link href="contrib.xml">Third-Party
                    Contributions</link>. The preferred submission method for patches is:
            </p>
            <ul>
                <li>Post to POI developers list</li>
                <li>Describe the patch, the reason for it and (if necessary) why this is important.</li>
                <li>Generate the patch in
                    <code>diff -u</code> format from CVS
                </li>
                <li>Also generate a documentation patch or new file, if this is something that should be documented.
                </li>
                <li>Post as an attachment rather than inline (unless it is trivially small).</li>
            </ul>
            <p>Following the above guidelines will facilitate your patch being reviewed
                and applied efficiently.</p>
        </section>
        <section>
            <title>Patch Queue</title>
            <p>
                <strong> [Under Construction] </strong> Archive links will be added later.
                <strong>Please do not bother the patch submitters/authors</strong> without first reading the
                relevant post(s) in the
                <link href="mail-archives.xml">mailing list archives.</link>
            </p>
            <p>Vapourware will not be listed.</p>
            <table>
                <tr>
                    <th>id</th>
                    <th>Summary</th>
                    <th>Reviewer</th>
                    <th>Resolution</th>
                    <th>Status</th>
                </tr>
            </table>
            <p>See also additional list of patches to be added in
                <link href="todo.xml">To Do</link>.
            </p>
        </section>
    </body>
</document>
