Re: TODO list for the next release

[Brian Jones]

Mark Wielaard <address@hidden> writes:

> - Check and apply patches in Savannah bugdatabase
>   <http://savannah.gnu.org/patch/index.php?group_id=85>.
>   A lot of the patches that Intel submitted were set to postponed but
>   the copyright assignment papers have been sorted out so they can go in
>   now.

The FSF has a signed document, but it failed to define developer
names, so RMS is not going to sign it until they get a letterhead
defining whose contributions count.  So I set the patches to postponed
again.

> - Add workaround for compiling with gcj (3.0.x and 3.1 CVS). I have two 
>   workaround for compiling with gcj in my local tree. It might be a good
>   idea to apply them.

Is there some way to detect gcj version and apply the right workaround
as needed?

> - Check and update README, HACKING, NEWS and webpages for new release.

Right, some of this is done already but needs updating especially with
regards to AWT.  

> - Figure out why "make dist" does not work.

I suspect some Makefile's including Java source need updating.  I can
probably fix anything else as well.

> - Check build instructions when make dist does work so people can easily
>   download the Classpath 0.03 and the ORP 1.0.9 release on a clean
>   machine and get it working out of the box.
> - Make release announcement for announce newsgroup, Freshmeat, etc.

Could you do this?  Aaron made the original announcement on Freshmeat.

> Fun to have but not neccessary/to much work for 0.03:
> - Popping up a AWT window with ORP
>   (I have seen it "work" under gcj but cannot get it working with ORP.)

I'd love to have the AWT in the same quasi working condition with ORP.
I'll look into that today.  The superbowl is boring between
commercials anyway.

I still have access to the ftp area on alpha.gnu.org as far as I know
so I should be able to make a release available when we're ready.

-- 
Brian Jones <address@hidden>