0.05

[Brian Jones]

For those who aren't aware, gcc is preparing a 3.3 release in a couple
of months.  I'd like to make a new Classpath release, perhaps in the
next few weeks, depending on how long it takes to get most of the
things below accomplished.  So below I borrowed heavily from the
format of Tom's email to the gcj list earlier.

There are still a number of bugs, patches, etc. I want to have fixed
or integrated before making a new Classpath release.

My current list:

* Integrate any remaining patches on Savannah as needed.
* Fix Classpath bugs found by running Mauve with GCJ, Kissme, ORP, or SableVM.
* Fix FilePermission bugs reported on Mauve mailing list.
* Bugs 744, 835, 1190, 1966 (this is all the bugs) on Savannah
* Import/CVS link in classpathx jaxp.  This includes all files that
  are part of org.w3c.dom, org.xml.sax, javax.xml, related gnu.* from
  classpathx jaxp project.
* Resolve javax.sound - http://tritonus.org/
* Resolve org.ietf.jgss - http://www.ietf.org/rfc/rfc2853.txt
* Resolve the org.omg.* issues and implement whatever we decide.
  Currently, this is something I need to followup on.
* Ensure support of GNU Crypto as a full security provider.

Comments on this list, suggestions for additions or removals, etc,
welcome.

I think our release criteria should be:

* Work with Kissme and JRVM, SableVM, and ORP if possible from the release.
* Pass Mauve test suite with 0 FAIL (we need a means of XFAILing tests
  we know we won't fix).
* Full javadoc generated by gjdoc available for general consumption.

Again, comments welcome.

Without a working AWT I don't believe we can release a 1.0+ version of
Classpath.  So the version numbers should probably continue to
simply increment until there is a working AWT.

Brian
-- 
Brian Jones <address@hidden>
http://www.haphazard.org/~cbj/