bug-tracking

This might be a stupid question, but if I'm a lone developer and only ever going to be working off of my development laptop, how important is using bug tracking software? I am currently debating between using Subversion or SourceGear Vault as my VCS of choice, and SourceGear has an integrated bug tracker (Fortress) while the Subversion world tends to use something like Trac. Now, I am going to use my laptop for both home and work projects (I have an MSDN subscription for myself, and seeing as work is too cheap to buy me anything I'm going to write their software on my laptop to use it; we have

In my current company there isn't clear understanding between the test and development teams as to how severe a bug should be? There are arguments which go back and forth to reduce or to increase the severity. We are not as of now aware of any documents which lays the rules. The tester raises the bug and assigns priority based on his intuition. The developer would request a change based on his load or some other factor. How are severity/priority of bugs classified? Are there any standards which guide how software defect priorities needs to be determined based on customer needs, time lines and

Questions #1 through #4 on the Joel Test in my opinion are all about the development tools being used and the support system in place for developers: Do you use source control? Can you make a build in one step? Do you make daily builds? Do you have a bug database? I'm just curious what free/cheap (but good) tools exist for the small development shops that don't have large bank accounts to use to achieve a positive answer on these questions. For source control I know Subversion is a great solution, and if you are a one man shop you could even use SourceGear's Vault . I use NAnt for my larger

I noted that in BitBucket when your commit log contains a number like #12 this number is linked to the bug number 12. I found this feature interesting, and I wonder if there is any keyword that would allow me to mark the issue as resolved from the commit log instead of going to the web interface each time. If BitBucket doesn't do it, could you point a system that does? Rob Van Dam Bitbucket already supports marking issues on commit using the Issues service . The issues service scans commit messages for commands which will automatically change the state of the relevant issue on the tracker.

Several times now I've been faced with plans from a team that wants to build their own bug tracking system - Not as a product, but as an internal tool. The arguments I've heard in favous are usually along the lines of : Wanting to 'eat our own dog food' in terms of some internally built web framework Needing some highly specialised report, or the ability to tweak some feature in some allegedly unique way Believing that it isn't difficult to build a bug tracking system What arguments might you use to support buying an existing bug tracking system? In particular, what features sound easy but

As the title says, I'm starting one project right now, and trying to layout the infrastructure for the project (SVN, Email, Bug tracking, Online Forums, etc...) So, Bugzilla or Mantis? Corey Trager I think you'll find that your team will like either Trac or Redmine more than Bugzilla or Mantis. Both integrate nicely with Subversion. Both include wiki, forums, project management features... Quick overview: Trac : Very widely used and loved, written in python, huge community, lots of "plugins". A common complaint is that it doesn't support multiple projects out-of-the-box, but you can add a

Relevant information: issue 3602 on GitHub I'm working on a project that gathers and tests public/free proxies, and noticed that when I use the curl_multi interface for testing these proxies, sometimes I get many 28(timeout) errors. This never happens if I test every proxy alone. The problem is that this issue is unreliably reproducible, and it does not always show up , it could be something in curl or something else . Unfortunately, I'm not such a deep networks debugger and I don't know how to debug this issue on a deeper level, however I wrote 2 C testing programs (one of them is originally