Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: is released: 2.1

Upcoming commons-vfs2-2.

...

This is a list of things to do for the (upcoming) next release of VFS 2.1

  • check test dependencies, update them and finally resolve VFS-457
  • announce Java 1.6 in .vm / site
  • add 2.0 release (1.5) to download page (release.2....)
  • update testing/test-server site: some protocols are tested now, hdfs with windows profile
  • define the mave-release-plugin process (tags, RCs, votes)
  • fix multi-module checkstyle problem
  • decide on minimum hdfs version and update it, finally resolve VFS-530

After Release

2 release

  • News: Apache Commons VFS 2.1 has been released.
  • State: next release 2.1.1 or 2.2 is considered

Todo List for Releases

Things to be aware of

  • VFS is a multi-module project, sandbox is even optional (profile)
  • the maven-release-plugin does not work very well with the current release strategy of Apache Commons (Tag after vote)
  • tag conventions in the 2.0 release have a bit messed up the repo. The 2.0 release is named (VFS-1.0 vs. commons-vfs2-project-2.0)
  • 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. The report is not prominent, so we will create it incomplete.

After Release

  • Mark Version as released, clsoe all resolved Bugs in Version. Change Fix Version for unresolved bugs
  • open next snapshot
  • DOAP fileclose all 2.1 bugs (resolved->closed)