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."
...if Bugzilla had a bug.
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.
I found a bug. Where do I report it?
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.
I mean, wow. Most people spend years waiting for 2.0, or 3.0, but for me the magic milestone is the glorious 2.18!
January 15 lists two entries ... talk about last minute programming!
Gamercentric.com - GAMING HEAVEN
"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
Err, wasn't this comment supposed to be on another thread or something?
The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
... thats alot of dependencies.
And it still requires MySQL. Sorry, but that's a deal breaker.
I don't care about bugs displaying fast, bugs are important, so unless there is a way to run with PostgreSQL or another actual database, it's not of any use to me.
Now for my front end proxies, MySQL is the shit.
- Adam L. Beberg - The Cosm Project - http://www.mithral.com/
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.
WOW! Did michael shit in your coffee or something? If so, shame on him. If you take slashdot this seriously, you have major fucking issues bud. OTOH, I laughed my ass off at your blurb here. Was that the intended reaction?
Screw michael, screw slashdot, and screw paying for premium membership. I enjoy reading as an anon, and always have Firefox block the ads that show up.
Would we be celebrating a revision of bug tracking software.
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 Ensim/Cpanel/Helm/whatever).
There are a lot of Bug tracking/help desks systems out there, I'm currently looking for different alternatives, if being root on the box is a must, it's unfortunate (I don't need the arguments on why that is the case and all, I am not complaining about it, just pointing it).
So if there is such a "web-based" branch, I'm sure it would get even more people's attention.
Thanks to whomever helps.
--- Metamoderating abusive downgraders since my 300th post.
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!
Don't look now, but I think we've all been mod-slapped. Thank you, Michael!
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
Looking at the install guide, it says you need mySQL. For those who prefer PostgreSQL, does anyone know if Bugzilla works with it?
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 would seem you've changed your canned response a bit...
I think it was a little more believable before, though.=p
web apps ever developed. Wow, it stinks.
Too bad it still looks like shit.
Aesthetics are everything for common adoptance people! When will you realize this?!
no. who are they?
with these systems is that you have to guess what category to report/look-up the bug in. I wish I had a nickel for every time someone's gotten snippy with me "Why'd you report that under 'GUI'? It's obviously 'useability'".
No folly is more costly than the folly of intolerant idealism. - Winston Churchill
>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.
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.
A good example of this is Thunderbird "bugs" filed about its non compliance with "good netkeeping seal of approval" standards.
lol :D
The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
http://shit.slashdot.org/article.pl?sid=05/01/16/2 045245
Holy shit, that was the funniest post I have ever seen on slashdot. I seriously almost choked to death. Damn funny.
Lots of big MySQL users around.
Treehugger? Treehugger... Treehugger!
That's not even right. I have personally seen the term used well before CD-ROMs were in wide usage, and the Jargon File reports that it is old enough that "golden tape" was used.
Don't know if this is a troll or not, but Bugzilla is pretty flexible. If you want to have strict access controls on BZ based on the owner, you can (and I suspect that this is how the mozilla instance is configured, but I've never used it), but that's certainy not required.....
-Kelly
Has the usability been improved since the version they are running for Mozilla? Bugzilla has to have one of the absolute worst user interfaces I have ever seen. And that's not worst as in "aimed at expert users", but worst as in "throw every feature you can think of on a single page".
I hate to flame, because despite the user interface, it's the best Free bug tracker I have seen. But they really need to do something with the UI. Is it really necessary to see a list of everyone who is watching the bug every time you view the bug? Is it really necessary to list the summary twice - once at the top of the page, and once for the 0.001% of the time you need to edit it? Is it really necessary to list about ten different tickboxes, drop downs and radio buttons to change the status of a bug, even though the majority of people not only won't want to, but won't have the permissions to?
most everyone in the company finds it pretty annoying to use and the UI looks like it was designed by a 10yr old.
;) I do agree on the "looks" though, they are pretty lame.
Personally I love bugzilla and they have to use it cuz I say so
Will the patches patch an .rpm install?
This guy is way out there
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
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.
Bugzilla is a critical part of the Free Software process - many projects rely on it and benefit greatly from its use.
Depending on your needs, Bugzilla may be overkill for your own (inhouse) project. From what I read on various blogs, it's somewhat hard to administer and/or install. So if you need a bugtracking system, check out this commented list of alternatives. Most of the systems in the list are free.
Wenn ist das Nunstruck git und Slotermeyer? Ja!... Beiherhund das Oder die Flipperwaldt gersput!
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 am NOT installing MySQL just to run it, no matter how good it is, same goes for MediaWiki - what is it with developers these days that they dont see the bigger picture and add abstraction layers from day one?
ad mailing interface, you can if you really want. I.e. the ELinks Bugzilla has an email interface which works fine. It was only as a contrib/ patch in 2.16.3, dunno about 2.18.
ad 1), that's just a configuration issue. By default, Bugzilla lets anyone registered do basically anything.
ad 2), if you mean it to allow "offline bugfixing" (while sitting in an airplane), I think it just wouldn't fly. There is much greater potential for conflicts (which are more annoying to resolve) and it isn't really that difficult to just do it manually.
It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
I hope they fixed bug #41233 "Fix problem with sucking"
While I realise that MYSQL is a viable back end DBMS on windows, I would like to know if there is any provision to use an ODBC data source and store data in different DBMS - such as SQLServer, DB2, Oracle etc. ? If not in version 2.18, then is this planned for any future release?
Does it work with mod_perl yet? This was the biggest obstacle the last time I had a look at installing Bugzilla.
I'm curious if anyone has experience using Bugzilla and GForge.
It looks as if Bugzilla might just be bug handling, while GForge is for an entire project management, including the funtionality of CVS/subverion.
Sometimes the AllInOne approach is fast, flexible and easy to learn. But sometimes not.
I'm wondering which way to go on a new project.
"Provided by the management for your protection."
Its as if they haven't heard of perl DBI: THE db abstraction layer. Why can't they make use of it ?
Oh, probably because once you learn to use features such as subselects which real databases offer then you can't go back to using the non-standard un-featurefull MySQL.
I know that I just landed a large documentation patch about getting Bugzilla to work with IIS about a week ago.
i on.html section 2.2.4.2 - Microsoft Internet Information Services.
check out http://www.bugzilla.org/docs/2.18/html/configurat
if you mean it to allow "offline bugfixing" (while sitting in an airplane), I think it just wouldn't fly.
Please turn off all electronic devices especially bug tracking software as it could cause the plane not to fly.
Sorry, that was not my post. In fact, it is extremely rare that I post AC. And when I do say something flamish, I say it under my own name. Sadly, I do not spend anytime (nor have I) flaming or bad mouthing the Mac... now Linux... I spend plenty of time on that horrible topic.
Help Brendan pay off his student loans
2.18 is gone from the /pub/mozilla.org/webtools. you have a 2.16.x stable release and a 2.19.1. no 2.18 except release candidates. the download link from the bugzilla webpage gives a 404
I was referring to aldoman's post. He posted a mac flame once before that was nearly identical. Lat time he posted anonymously, though.