Release Plan For BeanUtils 1.7.0

Background

This is primarily a service release aimed at allowing downstream users to use BeanUtils with either commons-collection 2.x or 3.x. There will also be significant changes in packaging and the introduction of beanification.

The release is still in the advanced planning stage but it's important that it's done promptly.

Status

Final preparations.

Pre Release Tasks

Bean Collections

Web Site

• Create basic website DONE
• Basic integration with BeanUtils DONE
  

Source

• Review names for methods and classes DONE
  

Documentation

• Review documentation to ensure that those classes in bean-collections are clear DONE
• Add documentation on any classes in bean-collections which have not been covered already DONE
• Ensure bean-collections classes are properly javadoc'd DONE
  

Beanification

• Review method names and accessibility for new method DONE
• Think about introducing abstract classes for the beans DONE
  

I've taken a look at the new beans and I think that probably the original policy (matching them with the method names on the static methods) is about right. Will probably all change when we are able to break compatibility...

Collections Compatibility

• Create unit tests to make sure that BeanUtils works with collections 2.1 and collections 3.0 in the classpath. DONE
  

General

Bug Review

No bug review for this release.

Check Compatibility

This release should be binary compatible with the last 1.6.1 release. DONE

Release Plan

CVS

A release branch will be created (RELEASE_BEANUTILS_1_7_0_BRANCH).

Release Notes

These will be prepared in the traditional fashion. DONE

Release Candidate

A release candidate will be prepared and some time will be allowed for review and testing before moving to the release VOTE. DONE

Up to BeanUtils