RC3: Call for Bug Reports

[Colin F]

I'm pleased to say that we are gearing up here to release vB 3.5.0 RC3 in the coming days, but before we do so I'd like to make an appeal for bug reports.

Unfortunately with many recent releases, particularly of 3.5 RC1 and RC2 we have made the release, only to be inundated within hours with many bug reports, detailing problems that existed before the release of the latest version.

This makes development very difficult, so this is a request for anyone that thinks they may have found a bug in vBulletin 3.5 in its current incarnation to formalize the problem by making a bug report here (http://www.vbulletin.com/forum/bugs35.php).

Please don't leave the problem to someone else, thinking that someone else may have found the problem and will report it - if you believe that you have found a problem, please report it yourself!

It doesn't matter if the problem is minor or major, and it doesn't matter if what you think is a bug turns out not to be so - the worst that can happen is that your bug report is labelled as bogus and nobody will think any less of you for making the report.

The only other thing I would ask is that if you make (or have made) a bug report, please keep an eye on it, as the developers may ask specific questions that you will need to answer in order for the problem to be reproduced and rectified.

Thanks everyone.

This was posted by Kier on the vBulletin.com forum.
It would be great if the coders and users here also reported anything they may come across.

[Oblivion Knight]

Hrm.. I wish Kier made a discussion thread based on that announcement as I'd have loved to voice my personal opinion on the fact that only recently have bugs been reported that date pre-RC status.

I only upgraded to RC2 recently because I decided that the majority of major bugs in 3.5.0's code would have been discovered by now.. Any bugs that I've come across, I have reported them and I'm sure it's the same for several others too.. If bugs are still coming in throughout the RC's, it's simple; don't release the Gold version until it is ready. The whiners can wait, an unstable 3.5.0 option is there - it's up to them if they take it or not.

[amykhar]

I know that I recently found some bugs in areas that I don't ordinarily use that often. I think the more obscure bugs are coming out over time.

[sabret00the]

I didn't know that people were moaning for the GOLD version, though it is quite sad to hear that pre-RC bugs are still being reported when in actual fact we need to squash these things as soon as their found, oh well it all makes a better product i suppose.

[nexialys]

pre-Rc bugs are always reported because people are not updating their 3.5 ... that's all...

also, if no new bug is found, maybe it's because the release is stable... i don't see why we always have to have hundreds of bug reports per day... ;)

[Paul M]

TBH, I think they need to be more positive to bug reports - having your report labelled as "bogus" is a term that will put many people off ever reporting again - and indeed, the reaction to some of the bugs I have posted has dented my enthusiasm on reporting any more. :(

[Erwin]

TBH, I think they need to be more positive to bug reports - having your report labelled as "bogus" is a term that will put many people off ever reporting again - and indeed, the reaction to some of the bugs I have posted has dented my enthusiasm on reporting any more. :(

Not a bad point to raise. :) Maybe repost that at vB.com.

[sketch42]

Not a bad point to raise. :) Maybe repost that at vB.com.

yea i never understood that... why not just lable them [Solved] because in the end thats really what they are no? meaning bug or not the issue has been resolved

[Brad]

yea i never understood that... why not just lable them [Solved] because in the end thats really what they are no? meaning bug or not the issue has been resolved

'Solved' would make it look like it was really a bug. Honestly the bogus label doesn't bother me, it's used nearly everywhere anyway.

[peterska2]

Bogus is a bit of a pain. I hardly ever report bugs but that's probaly because my site doesn't get hammered in the same way as most others do. When I do find something though I always report it and then it's either labelled as duplicate, which I don't mind, or bogus, which makes me think 'Why bother?'

[Boofo]

"Works for me" is the one I don't really like. We get enough of that here already.

[nexialys]

ya.. terminology in the bugs system of vb.com is not really userfriendly, but it's the usual terms used in commercial/pro bug reports... if you don't like the terms, just forget the terms...

it's like working at McDonald, you may not like ketchup, but you will continue to make BigMacs for the clients anyway...

[Princeton]

"bogus" could be "False" (as in false report)
"Works for me" could be "Cannot reproduce"

[Boofo]

Works for me almost sounds like a brush-off where Cannot reproduce at least sounds like they are trying to find it.

[Brad]

Works for me almost sounds like a brush-off where Cannot reproduce at least sounds like they are trying to find it.

Cannot reproduce would imply that the issue does not exist at all. :)

'Bogus' as been used for years in most of the bug trackers I've used. Keep in mind that this system is mainly for the developers and it doesn't have to be that user friendly.

[Paul M]

Cannot reproduce would imply that the issue does not exist at all. :)as does "works for me".

'Bogus' as been used for years in most of the bug trackers I've used. Keep in mind that this system is mainly for the developers and it doesn't have to be that user friendly.If they want users to report bugs, as Keir has requested, then it needs to be user friendly.

[Boofo]

Cannot reproduce would imply that the issue does not exist at all. :)

Well, it wouldn't exist at all if they couldn't reproduce it, would it? ;)

[Princeton]

Well, it wouldn't exist at all if they couldn't reproduce it, would it? ;)

LOL

'Bogus' as been used for years in most of the bug trackers I've used. Keep in mind that this system is mainly for the developers and it doesn't have to be that user friendly.
Everything should be user-friendly rgardless of group.
Only because HELLSATAN jumps over the bridge does not mean that BOOFO has to? :D

[nexialys]

Only because HELLSATAN jumps over the bridge does not mean that BOOFO has to? :D Oh, we lost HellSatan ?! :rolleyes:

[Boofo]

LOL


Everything should be user-friendly rgardless of group.
Only because HELLSATAN jumps over the bridge does not mean that BOOFO has to? :D

Well, I'm glad we cleared that up, because I wasn't sure what I should do after hellsatan jumped. ;)

[Princeton]

Roflmao

[Paul M]

Well, I'm glad we cleared that up, because I wasn't sure what I should do after hellsatan jumped. ;)Party ? .....

[Brad]

If they want users to report bugs, as Keir has requested, then it needs to be user friendly.

Something that is "bogus" is something that is useless, bad or fake.

Example: This calculator is broken, it gives bogus results.

I really don't care much if it is changed, I suppose I just don't see how someone can get mad because their report was labeled bogus. All of these long-winded suggestions begin may do the same thing and I've yet to see anyone suggest something that everyone agrees on.

'User friendly' may not have been the right word for my last post. What I was trying to get at is the fact that this system has to be 'developer friendly'. The terms they are used to allow them to seperate the reports quickly when going over them.

It really doesn't matter what label you give it, there are always going to be a small number of users that get mad because what they report isn't a bug.

Again it doesn't matter to me if it is changed, I can't belive I devoted my time to posting this ;)

[soniceffect]

I think the point is still there and a valid one ... People who use RC software, in my opinion should have the curtusy to report any bug that they find. If this isn`t the case, they may as well not release it, as this is what it is for. I tend to agree with brad. I ain`t a coder, but who cares what they label the bug report I post... I`ve posted it, I`ll live to see the fantastic gold version, if they wanna say "Hey ya dosey git, this one was posted the other day" I wouldn`t care. It should give people some satisfation knowing that people are reporting things fast, and these things are being sorted fast.

[spence2]

Although I will never quite understand why people who claim not to care "waste" their time enlightening us with the knowledge that they don't care ... :ermm: ... the term "bogus" has been changed by Michael at vB.com to "Not A Bug".

[Revan]

Im offended by the term "Unconfirmed" since it gives the impression that no-one has bothered to even look up the bug I reported purely out of the kindness of my heart.
[/sarcasm]

Im sorry, but what this topic has turned out to be... I don't know whether to laugh, cry or shoot whoever claims they are offended by "Bogus".
And before you go shouting "You haven't ever reported a Bogus bug, you don't know what you're talking about!!!!1111one" then read it and leak saltwater (http://www.vbulletin.com/forum/bugs35.php?bugstarterid=52573).
For the lazy ones, my report stats goes as follows:

2 Bogus
1 Works For Me
3 Working as Designed
1 Duplicate
7 Closed (fixed) (though I know my Unconfirmed one is gonna add to this)
1 Browser bug/issue

Did I feel stupid when I reported something that later turned out to be my own fault/just bogus? Sure.
Did I stop reporting bugs because I had a few reports off the mark? No fking way.
Why? Because I love this software, and I would rather have wasted 1 minute of a developer's time by forcing him/her to type up a quick reply explaining the matter, than have caused an user (who may not have the knowledge to detect/report the bug him/herself) grief because of the bug.

If anyone pulls any more of this crap, Im gonna register the domain "carebears.org" and redirect it here :p

[twoseven]

you going to have the 'carebears stare' as well revan?

[Mr Blunt]

I have to commend jelsoft about this, honestly. They have been kind enough to offer solutions to me when my "bug" gets listed as "not a bug" ... like for example the custom permissions install fix. John didn't HAVE to take the time to point out the relevant code lines that we coders need to reproduce in our scripts .... but he did .... so subsequently I showed KirbyDE the response and he now has a fix for this in his custom permissions how-to thread.

Another example ... even though stopping the page redirect during a product installation was a "suggestion", Mike was kind enough to listen to my reasons why I feel it's a "needed feature" and subsequently he will be turning this into an option for RC3 coders.

My point is good things can result from even issues deemed not to be bugs.

I'm NOT saying that suggestions should be posted there ... because you SHOULDN'T ... but if it's something you feel really really needs to happen before gold, then I do recommend "stating your case" to them. If your nice about it, maybe they will do something about it anyways.

Like they said in their announcements thread...
They won't think any less of you if a bug is reported to not be a bug.
Leave the egos at the door guys!!!
We ALL want a stable release.
Them as much as us.
AND THAT BUGS FORUM IS WHAT MAKES THAT HAPPEN!!!

Use it ... and if need be ... ABUSE IT SLIGHTLY since we are in the home stretch!!

[Andreas]

17 Fixed
1 Flagged for Future Version
1 Confirmed
1 Unconfirmed
3 Bogus (1 was /me being dumb, 1 is actually a "Feature" and 1 was classified as a Feature-Request - but implemented :))


Not that bad at all ;)