[Ivy Wiki] Update of "IvyFirstApacheRelease" by XavierHanin

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The following page has been changed by XavierHanin:
http://wiki.apache.org/ivy/IvyFirstApacheRelease

------------------------------------------------------------------------------
  
  == Migration ==
  
-  * New accounts
-  * SVN import
-  * Jira import
-  * Docs import.
+  * New accounts '''done'''
+  * SVN import '''done'''
+  * Jira import '''done'''
+  * Docs import. '''done'''
  
  == Code changes ==
  
-  * Move source to apache package. Issue: package name? org.apache.ivy? org.apache.antlib.ivy?
+  * Move source to apache package (org.apache.ivy)  '''done'''
-  * Move antlib declaration, but retain a reference in the jayasoft package.
+  * Move antlib declaration, but retain a reference in the jayasoft package. '''done'''
+  * Add Apache headers  '''done in java source files'''
-  * Add Apache headers (Stefan B. has a perl script to monitor this), or use checkstyle
+   * (Stefan B. has a perl script to monitor this), or use checkstyle
+  * Refactorings easing further development contributions '''done'''
+ 
+ '''postponed after alpha release'''
-  * Showstopper bugs: (list)
+  * Showstopper bugs: (list) 
   * Non-backwards compatible API changes that can then be kept stable.
-  * Refactorings easing further development contributions
  
  
  == Build changes ==
  
-  * Build under Gump
+  * Build under Gump '''done'''
+ 
+ '''postponed after alpha release'''
   * <antunit> tests. 
   * publish artifacts on the Maven repo
  
  == Tests ==
  
+ '''postponed after alpha release'''
   * various ivy.xml, 
-  * ivyconf.xml with various options
+  * ivysettings.xml with various options
   * buildlist tests with complex depth; ivy files containing relative paths for inclusion
   * handling particularly troublesome POM files. e.g those with unresolved variables, those with bad dependencies (the pom2rdf audit can find these)
   * troublesome ivy files (preferably user supplied)
   
  == Doc Changes ==
  
+  * Format? => Xooki '''done'''
-  * Format?
-  * Can JCite be used to pull in Java source?
-  * Change references & URLs.
+  * Change references & URLs. '''done'''
+  * add a release guide to the wiki
+ 
+ == Misc ==
+  * add NOTICE
+  * update LICENSE '''done'''
+  * add RELEASE_NOTES
+  * update DISCLAIMER
+  * include NOTICE, LICENSE and DISCLAIMER in jar manifest
  
  == Timetable ==