You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Apache Wiki <wi...@apache.org> on 2016/05/19 18:32:06 UTC

[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.

The "VfsReleaseState" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=20&rev2=21

Comment:
is released: 2.1

- = Upcoming commons-vfs2-2.1 release =
+ = Upcoming commons-vfs2-2.2 release =
  
-  * Preview of Site: N/A
+  * News: Apache Commons VFS 2.1 has been released.
+  * State: next release 2.1.1 or 2.2 is considered
  
+ == Todo List for Releases ==
- This is a list of things to do for the (upcoming) next release of VFS 2.1
- 
-  * explain/resolve clirr incompatibilities
-  * create and commit RELEASE-NOTES.txt (Java6, hadoop - draft with all changes checked in)
-  * step through the release process for software and site
  
  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). It might be easier to not use it
+  * 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)
-  * vfs site is a post 2.0 snapshot with broken links (SVN version is better but not published yet)
-  * hdfs support is new, needs to be announced and explained (write mode VFS-570 is missing)
   * 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
   
-  * close all 2.1 bugs (resolved->closed)
+  * Mark Version as released, clsoe all resolved Bugs in Version. Change Fix Version for unresolved bugs
   * open next snapshot
   * DOAP file
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org