« 2004-11-19 Trunk builds
Aviary branch landing in progress »

2004-11-21 Trunk builds

  • Fixed: 265987 - [Security hole] Any tab can replace contents of current tab.
  • Fixed: 269585 - [Topcrash] Trunk crash at nbc.com opening a new window.

Windows builds: Official Windows, Official Windows installer (discussion), BlueFyre's O2 G7 SSE, stipe's O2

Linux builds: Official Linux, Official Linux installer

Mac builds: Official Mac

This entry was posted on Sunday, November 21st, 2004 at 5:54 pm and is filed under Trunk. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

6 Responses to “2004-11-21 Trunk builds”

  1. LinkTiger Says:
    November 21st, 2004 at 7:33 pm

    Bugzilla says that Bug 269585 (crash @ nbc.com) is ASSIGNED, not FIXED.

  2. Jeff Walden Says:
    November 21st, 2004 at 9:39 pm

    Look at bonsai logs, LinkTiger: they’re the only real source of information there is, because bugs are always updated after the checkins are made, and sometimes bugs remain open just to keep the issue on the radar for possible regressions. I don’t know what the specific issue is here because I haven’t read the bug, but I do know bonsai’s your best source.

  3. Guenter Says:
    November 21st, 2004 at 11:32 pm

    Have you seen
    http://www.saintpatrickdc.org/bsmedberg/

    Build changes on Trunk

  4. darkdazzle Says:
    November 22nd, 2004 at 2:57 am

    I think after moving to Trunk you should update
    the list of sources either by adding 1.1 or
    removing 1.0 bugzilla links

  5. Jean-Marc Gillet Says:
    November 24th, 2004 at 8:50 am

    Something I didn’t know until now : seeing a bug assigned to “nobody” doesn’t necessarily mean that the main developers don’t have interest in fixing it. Some bugs are assigned “in private” and only get assigned when the work has started.

  6. Hank Roberts Says:
    November 29th, 2004 at 9:01 am

    So — anyone familiar with the OSX build able to advise me whether I can usefully test for bugs yet? I’m not a programmer, all I can do is break things and report. Which, I realize, isn’t useful for a while ’til the trunk is ready for that testing.

    Say when, someone — or a pointer to any OSX specific info?