Slashdot Mirror
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."
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.
--
What short sigs we have -
One hundred and twenty chars!
Too short for haiku.
It's not irony for Bugzilla to have a bug... the irony would be if a Bugzilla bug prevented the same bug from being reported and fixed.
Help Brendan pay off his student loans
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.
"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.
Sincerely,
Pan Tarhei Hosé, PhD.
"Homo sum et cogito ergo odi profanum vulgus et libido."
Should we wait on Redhat or start looking?
This guy is way out there
Does anyone have a good comparison of Bugzilla and Fog Creek Bugz?
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 joelonsoftware.com guy) when creating Fozbug. Since you want to allow everybody to fix bugs (specially in OSS) everybody should be allowed to reopen or close a bug
2) distributed system. For a example of this, look at Bitkeeper in the linux development.
It's ironic that everytime someone uses the word 'ironic', somone else defines it for them.
LiveJournal? they seem to do pretty well with MySQL...sounds like they might be the biggest mysql user around? Just a guess.
No, I'm having a party at my house tonight to celebrate.
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?
- In Capitalist America, law violates YOU!
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.
-kgj
This is not irony, it is just that lots of bugs have self defense behaviours.
Rethinking email
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
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.
#6495ED - cornflower blue
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.
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.
.msi installer that would install Apache, MySQL, Perl and any other needed software to get Bugzilla up and running as easily as possible.
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 restrictions and a lot of usability improvements. Now bugzilla may be good for developers, but we should consider also other interest groups: product management, customers, customer support people, testers etc. All of these need better REPORTS in order to see what is the status of ***their*** issues.
- Easier installation. If Firefox can be installed by a Windows installer, so can Bugzilla. We could really use a simple
I hope they fixed bug #41233 "Fix problem with sucking"