THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Preview of Site: http://people.apache.org/~ecki/commons-vfs/
- Decided: will use manual not release-plugin process
- JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit, I plan to not create a JIRA report for the release (as all of them are in the chnages.xml anyway). . The report is not prominent, so we will create it incomplete.
This is a list of things to do for the (upcoming) next release of VFS 2.1
...
- OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - pending use and test commons-parent release
- only show aggregate checkstyle report toplevel
announce Java 1.6 in release-notes - create and commit RELEASE-NOTES.txt (Java6, interface changes in clirr report)
After Release
- close all 2.1 bugs (resolved->closed)
- open next snapshot
- DOAP file