Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates
 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=BL+jWu6XcFxPV5A98p4Uv2yOyt/AszwoYaPRWOaKa7Y9JNNuJlyCIRbWHDAVXEbTq9kO2gfZktqrmx2sSts9KkGFMd8/T3Uyxb7C3N6v6fCmeQtfexzs3p43BG0V1MkTHbknT+83ZyW4Nj5+jjWDgkzJ4X+F2SLJ4yYpFlbmQPM=
Message-ID: <31cc37360803182335o280f55c2vabc7154da6d369db@mail.gmail.com>
Date: Tue, 18 Mar 2008 23:35:38 -0700
From: "Henri Yandell" <flamefew@gmail.com>
To: "Commons Developers List" <dev@commons.apache.org>
Subject: [collections] 3.3 issues
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Here's a peek at some of the interesting issues in the 3.3 TODO list
that need discussion:

* COLLECTIONS-238 - Allowing ExtendedProperties to have empty values.
ie) "foo="  would result in a key of foo existing.

Is anyone concerned about backwards compatibility with that? I'm happy
with it - it seems to me that it is how that should have worked, and
people shouldn't be commenting out by removing the value rather than
putting a comment in front.

* Serializable - COLLECTIONS-240, COLLECTIONS-285, COLLECTIONS-221,
COLLECTIONS-267, COLLECTIONS-266. Basically we need some Serializable
test love.

* COLLECTIONS-265 is ready for committing. So any nay-sayers, speak
now or reopen later.

* Specifically for James Carman - how does Dave's patch to your
COLLECTIONS-194 look?


Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org