Bugzilla 2.18rc1 is out, and a new Bugzilla website

July 10, 2004 by · 2 Comments
Filed under: Bugzilla 

Well, after 2 years of waiting, we’ve finally branched for 2.18. Along with that comes our first release candidate for the upcoming 2.18 release. You can download it here.

This has been 2 years in the making, and the release process itself isn’t exactly a piece of cake, especially when we have security issues to deal with. Myself and 4 or 5 other tireless folks have spent the last 4 days getting very little sleep while we toss around draft copies of the advisory, finish up the checkins for the last few blocking bugs, and otherwise get all the details worked out. I think Gerv about summed it up better than I could.

We also have a brand spanking new design on the Bugzilla website. It’s a much more professional look than we used to have, and helps us blend in with the Mozilla Foundation a little better. I can’t express enough thanks to Mike Morgan, who redesigned the site for us based on mozilla.org’s existing CSS, and tweaking it enough to give us our own flavor. After what we’ve had for a website for the last few years, it really is quite a beauty to behold. We’d love to get feedback on the website design, or even content. If there’s anything you think should be done differently, you can either post on netscape.public.mozilla.webtools or file a bug.

  • Find me on Twitter

    Me: @justdavemiller
    The Bugzilla Project: @bugzilla
  • Recent Tweets by @justdavemiller

    justdavemiller The first public release of the Ubuntu OS was 10 years ago today. My memories of it at http://t.co/o2dSKulW5H
    justdavemiller RT @MitchellBaker: Liberia: The Impact of Open Source Software in the Fight Against Ebola: http://t.co/G3BeYnCZLF via https://t.co/hitm28YY
    justdavemiller RT @brianloveswords: If you use homebrew and you plan on upgrading to Yosemite, read this first: https://t.co/eHVFGn2UkC.
    justdavemiller @FCC and most browser block insecure content on secure pages now
    justdavemiller @FCC when viewing your website on https the video player on the live page doesn't work because it tries to load over http instead of https
  • Archives