Re: Preparing for 1.7 release

I have now manually converted the change log to release notes. AFAIK  
the release notes should now be up-to-date. I note, however, that we  
now have 12 disabled tests. This makes me very uncomfortable. I would  
like to place a priority on fixing those - ahead of addressing any new  
bug reports, patches, or RFEs; however, as long as we are going to do  
that, I see no reason that we shouldn't release 1.7 ahead of that.   
There are some other interesting things that have been happening that  
we should discuss, process-wise; again, I think we can put those off  
until after the release.

The one big issue that I see is that jdk 1.4 compatibility is broken.  
We get 36 broken tests, which seems to be related to some changed  
interfaces. I know that I had gotten that working in the past, and am  
not sure when it broke. That needs to be the top priority, as we  
cannot release without it. I am not prepared to drop 1.4 support at  
this time.

What else do we need to do before the release?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/