BugTrack?

[Arnie]

Is there a possibility that we can have a bugtrack style system somewhere that tracks bugs reported and shows us if they have ben fixed, and added to the new release somewhere?

It'd not need much more than a description of the bug found, a link to the posting made (if relevant) and the code change made etc..?

The main problem I find now if that if we report a bug, and than temporarily patch the issue, we don't know when the official fix will make it into the download release. I've been caught out before by downloading the current version that's online then found that it didn't have all the official fixes to date in it. This left me with bugs coming back that had previously been fixed.

[WB]

Good idea.

I think that would help.

[Chuck S]

What do you mean by a bugtracker system?

Usually it works like this. If I mark something FIXED it means the build has been sent to Michael for uploaded so anything documented on the forum fixed should be in the build.

When we get enough bugs to warrant a new build we issue a .01 .02 .03 release to the general population but our policy is to update our builds with any bug fix's ASAP as new customers or upgrading customers are not coming into the support forums reporting bug's that are already fixed.

[WB]

I was thinking something along the lines of:

http://www.vbulletin.com/forum/bugs35.php

It makes it much easier to see if a certain bug has been reported and what the current status is.

[Arnie]

Yeah, something that allows us users to see if our bug has been fixed and/or included in the current release.

Right now it's impossible for us that spot bugs to know if the present release (that's continually revised and updated) actually includes the relevant fixes or not.

I've already fallen foul to reporting a bug, which is noted and reported "fixed", then when I've downloaded the latest release that was updated that day (and probably should have included the fixes) it's not been fixed jsut yet, and when the upgrade is done bugs that were patched in the interim become "unfixed".

Whilst a forum is great to chat about submitted bugs, a simple free system (there's loads available) that allows us to submit a bugtrack in a standardised format to you and then track if it's fixed/not-fixed/included/rejected etc would be great. I'd not remove the forum that's here, but a companion to it that allows us to submit bugs allows those of us that are interested in helping out to be a bit more organised.


IMHO having a rolling 3.1 release with a static version number that doesn't change, yet with code that actually changes each day is a very bad idea. Otherwise it's almost impossible to track what's new in a release and what's been fixed.

[SaN-DeeP]

Indeed a nice suggestion,
there is an option/addon available on vb.org for a bug tracker, pp should consider addition of this.