COLLECTIONS 2.0 DIGEST (02/26/2002)
-----------------------------------------------------------

The following is a synopsis of the Collections 2.0 release
effort to date.


RELEASE NOTES DRAFT
-------------------
http://cvs.apache.org/viewcvs/jakarta-commons/collections/RELEASE-NOTES-2.0.
html


ISSUES
---------------

BeanMap: Needs to clean up unit tests, and make sure all variations
from "typical" Maps are documented in Javadocs.  IMO,
BeanMap is very light on JavaDocs

All Collections: There are definitely bug fixes that are not being
documented.
If you fixed bugs (or added new features) since 1.0, you will want to
document them in the release notes.


PENDING COLLECTIONS
-------------------

Collections from the Commons UTIL package:  Need to be integrated
into Collections 2.0.  Duplicates must be resolved.  (IN PROGRESS?)

DirtyFlagMap: Per the email sent by James House
(http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101406634514652&w=2).
Will be reviewed by Michael Smith

"Comparators" proposal: Commit proposed comparators to CVS for review.

unmodifiableIterator: Proposal sent to the mailing list
(http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101462232021093&w=2)


COMPLETED
---------

Copies of all Serializable collections have been checked into
CVS for compatibility testing.  Unit tests suggest that only
LRUMap has changed its External form.  (Note: these unit tests
are sanity checks only; they're not infallible.)  Michael and
I added lots of other new unit tests too.

Added descriptions (based on JavaDocs) of all new Collections
to the STATUS.html file.  There are still several 1.0
Collections that were never documented in the STATUS.html file.
Volunteers welcome.

Converted release notes to HTML and added descriptions of
all new Collections.




_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to