Graham Hamilton's Blog

Tiger Status: Release Candidate is out

This is a quick update on where we are with Tiger (J2SE 5.0).

We're now in the final haul, heading towards a target release date of September 30th.

The Release Candidate went out today: http://java.sun.com/j2se/1.5.0/download.jsp

This should be pretty much the final bits, barring any major show-stopper issues. Overall quality is looking good (I think Mark Reinhold will be blogging more about this soon).

The Tiger JSRs are now in Java Community Process Final Ballot and we hope we'll get the JCP Executive Committee final approval on the 14th.

Overall the release seems to be on track for final release on September 30th. We will be watching carefully for feedback on RC and we may do small schedule updates if needed, but we're hoping we'll be able to hit the 30th.

Now on to Mustang and Dolphin!

                                                                                                              - Graham

Comments

• *please* don't allow a release without fixing bug 4924220
  this is where font rendering under Windows is screwed

  i have a clean XP machine, a java1.5 build and simply opening the java control panel shows fonts where glyphs on often used characters (such as 'C','8') look extremely distorted

  not fixing this will mean another java release where non-technical users can easily tell Swing applications from native applications

  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4924220

  Posted by: asjf on September 02, 2004 at 08:31 AM

• *please* don't allow a release without fixing bug 4924220
  ps. well done on everything else :)
  

  Posted by: asjf on September 02, 2004 at 08:31 AM

• *please* don't allow a release without fixing bug 4924220
  +1

  I agree whole heartedly!

  Glaring UI bugs like this must be fixed before final releases.

  Posted by: cowwoc on September 02, 2004 at 12:26 PM

• unneccessary RW opening of /dev/(u)random in javac
  When I am running javac in a sandbox (gentoo emerge system), I am getting a sandbox violation every time javac starts, because it opens /dev/random or /dev/urandom with read-write flag. Before beta2, it opens it normally with read-only.
  I don't know, why this change was made, but it is a problem. And I see no reason to open the random device rw.

  Posted by: georgm on September 03, 2004 at 02:19 AM

• unneccessary RW opening of /dev/(u)random in javac
  To be sure this issue is noticed by the people who actually fix the bugs/get them assigned etc., I strongly suggest you enter a bug.

  If you provide the bug number here, people who wish to do so can vote for your bug, without doing a bug search.

  Posted by: ga24ga24 on September 03, 2004 at 08:59 AM

• unneccessary RW opening of /dev/(u)random in javac
  I filed a new bug report.
  Bug ID is 301942.

  Posted by: georgm on September 04, 2004 at 03:32 PM

• Still many bugs
  There are still quite a lot of bugs to be fixed, many of them are regressions. Here are just the ones I'm monitoring:

  Possible to create an applet window with no applet warning
  A window created by an unsigned applet is not fully shown
  REGRESSION: Can't copy/paste/cut in native components with an applet (This one has unbelievably been deemed not important to fix for tiger)
  REGRESSION: Extra mouse click dispatched after press-drag- release sequence.
  Window is not activated when clicking on its title bar (This one looks like a KDE bug).

  
  On an unrelated note, a favourite of mine which takes 2 minutes to fix but hasn't been in 2 years is Components drawing animated images leak memory.

  Posted by: msasha on September 05, 2004 at 02:23 AM

• Still many bugs
  you made this sound really bad, particularily the memory leak.

  so i followed the link for the leak and, presto,
  there is a workaround.

  sure a fix is better, but c'omon - aren't you
  spinning this negative just a tad???

  Posted by: ga24ga24 on September 09, 2004 at 12:35 PM

This work is licensed under a Creative Commons License.