Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Bugzilla 2.18 Goes Gold

Posted by michael on Sun Jan 16, 2005 06:12 PM
from the until-they-invent-self-debugging-code dept.
bugger writes "After almost three years of development, the Bugzilla project has released long-waited Bugzilla 2.18. It contains many new features, a huge number of bug fixes, some security updates, and more. It is also the first Bugzilla version to run unmodified on Windows. In parallel, security release 2.16.8 and a new development snapshot 2.19.2 have been announced."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Mirk (184717) <<ku.gro.rolyatekim> <ta> <todhsals>> on Sunday January 16 2005, @06:17PM (#11381329) Homepage
    It took them three years to get from 2.17 to 2.18? At a rate of 0.0333 releases per year, it must have taken them sixty-five years just to get to 2.17. That means they've been developing BugZilla since just after the start of World War II, which means they really ought to have shaken all the bugs out by now. Better drop the word "bug" from the name, then.
    • by handy_vandal (606174) on Sunday January 16 2005, @07:02PM (#11381587) Homepage Journal
      It took them three years to get from 2.17 to 2.18? At a rate of 0.0333 releases per year, it must have taken them sixty-five years just to get to 2.17. That means they've been developing BugZilla since just after the start of World War II ...

      If you accept that the rate of bug discovery is constant.

      This is a hotly debated issue. For example, some Creationists assert that the rate of bug discovery has accelerated with time, and that BugZilla development began five to six thousand years ago.

    • Don't worry, the pace is about to pick up. I heard that 2.20 will be out in about two weeks. Seriously
  • by digitalgimpus (468277) on Sunday January 16 2005, @06:18PM (#11381342) Homepage
    For those who participate with mozilla's bugzilla installation for reporting bugs, that has been the test site for some time.

    So you have had most of those features for quite some time.
  • by Pan T. Hose (707794) on Sunday January 16 2005, @06:24PM (#11381376) Homepage Journal
    "After almost three years of development, the Bugzilla project has released long-waited Bugzilla 2.18. It contains many new features, a huge number of bug fixes, some security updates, and more."

    A huge number of bug fixes? You mean it contains built-in, preloaded bug fixes for future bug reports? I had no idea it was even possible but it surely sounds like a useful feature. I will also probably use those security updates, for I have a lot of open tickets asking for them. This is a very good news.
  • RPMs (Score:3, Funny)

    by LittleLebowskiUrbanA (619114) on Sunday January 16 2005, @06:30PM (#11381410) Homepage Journal
    Should we wait on Redhat or start looking?
  • by sanityspeech (823537) on Sunday January 16 2005, @06:36PM (#11381448) Journal
    Taken from the about page [bugzilla.org]:

    Bugzilla is a "Defect Tracking System" or "Bug-Tracking System". Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favorite of hundreds of organizations across the globe.
    • by darkpurpleblob (180550) on Sunday January 16 2005, @09:55PM (#11382446)
      Most commercial defect-tracking software vendors charge enormous licensing fees.
      Most commercial defect-tracking software vendors also provide usable search forms.
      • This might be considered a little OT but one thing that confuses me about how Mozilla itself implements this for their own products (Firefox etc.) is that it's used to report and discuss things that I wouldn't think are "bugs" such as feature requests, functions that don't work the way end users think they should, and complaints about "antifeatures". Some of them can be damn annoying but the software in these cases is working as designed.

        The reason "bug"-tracking systems are used this way is because it wo
          • It's really issue, change or ticket tracking, rather than bug tracking.

            But ChangeZilla, TicketZilla or IssueZilla aren't as clear as bugzilla.

            It's easier to overload the most common term, instead of using a general term that risks being ambiguous.
  • Does anyone have a good comparison of Bugzilla and Fog Creek Bugz [fogcreek.com]?
  • by Anonymous Coward
    I've always hated bugzilla, don't know why. Well, one of the reasons is why everybody uses it via a web interface, not through a mailing list (like de debian bug tracking system).This is one of the reasons why kernel developers don't like bugzilla - you've to waste too many time through the web interfaces

    A bug tracking system should help to the developers, it shouldn't be a wall you've to break. I think new ideas are needed.

    1) Bugs should not have owners. This is th approach taken by Joel (thy joelonso
    • 1) Bugs should not have owners. This is th approach taken by Joel (thy joelonsoftware.com guy) when creating Fozbug.

      You have this exactly wrong. From here [joelonsoftware.com]:

      "...every bug needs to be assigned to exactly one person at all times, until it is closed."

  • I'm a bit lazy when it comes to installing and trying things, now i've been going in the doc (well, very lightly I must admit) but from what I understand, I need to be root on the box on which I would like to install this nice app.

    Is there a way, branch, doc or something that someone could point me to to install this to a remote web server with perl and everything installed, but just not root access? (like most reseller packages out there, with db access and all, but no rights to install stuff outside Ensi
    • It's mentioned in the docs - root access is not a requirement unless you want to create, say, a virtual host to run it from (like bugs.mysite.com instead of mysite.com/~username/bugs) or need to install additional perl packages. That is really the most difficult part of the setup. The files can reside anywhere and will be served up provided you have perl set up as the interpreter for .cgi files and have the proper perl packages, as well as a mysql database (not necessarily root on the db server). It may req
  • I've used bugzilla before on projects that were solely internal. But now I'm working for a new company that does custom software development for outside customers. I'd like each customer to be able to log in and see their own bugs, but not any of the other customers' (ie, other projects') bugs. Of course, developers should see all bugs.

    So, is there a way to restricts the "products" that someone can see by login in Bugzilla?
  • Looking at the install guide, it says you need mySQL. For those who prefer PostgreSQL, does anyone know if Bugzilla works with it?
  • by JoeBuck (7947) on Sunday January 16 2005, @07:12PM (#11381640) Homepage
    This term originated in the games industry, meaning that when the game was ready to be shipped, a master CD has been pressed and delivered to the publisher for production. The gold CD is used to stamp out the CDs that are actually shipped. It means that the final version of the game has been made, but you can't buy it yet because it still has to be shipped.

    The bugzilla guys aren't doing anything like this; it's free software after all, and you can get it today; "goes gold" means you can't get it yet, you still have to wait for the production ramp-up.

    • My, aren't we pedantic.

      Actually, what you've described is the origin of this particular "figure of speech", but that's all that it is now and most people here understand it as simply meaning that a product has been released. The term is not being misused, it's simply grown beyond its original usage. English is full of figures of speech and if we had to carefully examine every thing we say and write to ensure that the expressions we use are exactly congruous with the original usage...well English would be p
    • Bzzzt! Wrong, please play again. The term was in use well before there was a games industry. The best explanation I have heard for the term is that it is derived from gold casting craft. You wouldn't waste any gold until the casting mold was "perfect".
  • Patch viewing! (Score:5, Informative)

    by ZiZ (564727) * on Sunday January 16 2005, @07:13PM (#11381641) Homepage
    This is a marvelous new feature. From TFA:

    Patch Viewer
    ------------

    Viewing and reviewing patches in Bugzilla is often difficult due to lack of context, improper format and the inherent readability issues that raw patches present. Patch Viewer is an enhancement to Bugzilla designed to fix that by offering increased context, linking to sections, and integrating with Bonsai, LXR and CVS.

    Now instead of just being able to see what's already changed, you can see what a proposed patch will change, where it will change it, and what the code nearby the patch is. It may seem like a small thing in any individual case, but this will likely save huge amounts of developer time.

    Props to the Bugzilla team! They've always had a fantastic product, and this release looks like more and better.

  • Will the patches patch an .rpm install?
  • spammer's paradise (Score:3, Insightful)

    by mixmasta (36673) on Monday January 17 2005, @01:43AM (#11383368) Journal
    I hope they have addressed the design flaws that allow spammers to harvest addresses from it with ease. There's no reason email addresses have to be displayed to everyone. For instance, I use slashdot with no problems without displaying my address.

    I seem to remember them implementing some kind of kludge that munges the '@' symbol with a character entitiy. I think that is too little, too late myself.

    Beware: 90% of the spam I receive comes from my mozilla bugzilla email alias. I won't be joining any more bugzilla's because of this, until it's fixed at least.
  • Bugzilla and Windows (Score:2, Interesting)

    by Anonymous Coward
    Bugzilla is one of the few Open Source applications that really have possibility for taking over significant "market share" at business world. But IMHO Buzilla still lacks several key features that would make it a really strong choise.

    Don't get me wrong. I have been using Bugzilla via web interface in a couple of ocassions and it has a lot of potential. Especially since other (commercial) bug tracking softwares are really crappy in general.

    What Bugzilla could really use:
    - Better user interface. We need re
  • by macmurph (622189) on Monday January 17 2005, @05:15AM (#11383956)
    I hope they fixed bug #41233 "Fix problem with sucking"
    • LiveJournal? they seem to do pretty well with MySQL...sounds like they might be the biggest mysql user around? Just a guess.
    • Build a brooker for mysql/postgree then or just put a hand into MySQL. Why not alter the bugzilla code to work with Postgree? That whining of yours, its pretty childish you know?

      Have it ever occured to you that the bugzilla coders might actually prefer MySql and thus do it the way THEY like it to be? I dont think the will apologize for not tending to your specific needs man.
    • This not an insightful comment. MySQL is a great database for a lot of uses.

      The parent post is the typical attitude that if something doesn't fit *my* use, or *I* don't like it, then it's shit.

    • Mantis [mantisbt.org] is planning support for MS-SQL and PostgreSQL in the upcoming 1.0 release. It already works well with MySQL, but if you're going to be choosy, Mantis is a very strong contender for the future and will definitely be competitive with Bugzilla.
    • Re:Wow... (Score:3, Informative)

      I don't know if you are aware that there is a PostgreSQL-aware version of Bugzilla [redhat.com] available. Red Hat is pretty big on PostgreSQL so they maintain that version. The link leads you to a bugzilla-redhat-20031120.tar.gz tarball but there are testing a new beta based on bugzilla 2.18rc3. Check it out [redhat.com].
    • Probably makes it easier to code. Then you don't have to bother generating different versions of a page based on user permissions, all you have to do is have it spit out a "fuck off" page at people who try to change things they're not allowed to change.