Bugzilla 2.18 Goes Gold
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."
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.
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.
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.
This flies in the face of science.
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 require some intervention from the sys admin, but you by no means have to be one. You can even substitute IIS if you want to. Most of the hurdles are cosmetic ones.
Redhat uses Postgres with their Bugzilla installation, and there is a thread about Postgres compatibility on the Mozilla bugtracker here:
4
https://bugzilla.mozilla.org/show_bug.cgi?id=9830
Yes.
As an administrator under Users->Select User->Edit User->Group Access
wikipedia also uses MySQL, though the latest version of Mediawiki supports Postgres
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:"...every bug needs to be assigned to exactly one person at all times, until it is closed."
Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
I don't know if you are aware that there is a PostgreSQL-aware version of Bugzilla 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.
Email Address Munging
---------------------
The fact that raw email addresses are displayed in Bugzilla makes it trivial for bots that spamharvest to spider through Bugzilla, in particular, through Bugzilla's buglists. This change adds HTML obfuscation of email addresses as they appear in the Bugzilla web pages.
For every expert, there is an equal and opposite expert. - Arthur C. Clarke