Actions for the first release
This is a list of things that need to be done to get a first release out, while still in incubation. The goal is to ship something early to build up the developer community and get more people involved.
Migration
New accounts done
SVN import done
Jira import done
Docs import. done
Code changes
Move source to apache package (org.apache.ivy) done
Move antlib declaration, but retain a reference in the jayasoft package. done
Add Apache headers done in java source files
(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)
Non-backwards compatible API changes that can then be kept stable.
Build changes
Build under Gump done
postponed after alpha release
<antunit> tests.
publish artifacts on the Maven repo
Tests
postponed after alpha release
various ivy.xml,
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
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
TBD