...

If you know of any frustration that developers have with collections, this is your opportunity to make a change - possibly for the next decade

Backwards Compatibility

Wiki MarkupThis release will be a "completely new" codebase and will offer very little binary compatibility with previous releases. All deprecated methods and classes will be removed, and return types will be altered where it is seen fit to do so (see \[https://issues.apache.org/jira/browse/COLLECTIONS-218 COLLECTIONS-218\]).

Type safety

As stated above, generics will be used to ensure type safety of collection apis. This renders casting methods (MapUtils.getDouble()) useless, and they will be deleted.

...

• the sf code attempted to maintain binary compatibility with the non-generic commons code. This release does not intend to have binary compatibility, and may be substantially different.
• since this is a rewrite, all generic conversion decisions will be reconsidered, and starting with an almost complete code base may actually hinder this.
  

Development

Wiki Markup\[wiki:/ProjectPlans Project Plans\] outlines the direction of the development[BR] \[wiki:/DevelopmentGuidelines Development Guidelines\] explains how the project is organised, how to get started, and most importantly, how to ensure that your contributions do not pose a burden to other developers[BR] \[wiki:/Contributors Contributors\] lists the people who development

Development Guidelines explains how the project is organised, how to get started, and most importantly, how to ensure that your contributions do not pose a burden to other developers

Contributors lists the people who are currently helping out with the project, and what they are working onare currently helping out with the project, and what they are working on[BR]