[DUG] A Friday Qustion on Monday.

[JeremyN at FrontierSoftware.com.au]

> If they released in their advertising "by the way there 
> are 200 known bugs in this new release as listed:" It 
> might make for a fairer choice when deciding to pay.

I guess there is a trial version for this

> I have no problem with the borland products.
> It is the integration features that cannot be disabled 
> properly that effect my development lifecycle.

There are ways to disable any package in the IDE

> I hope you are not hinting that if you don't pay 20,000 
> per person for lifecycle tools, then you can't be doing it right? 

nope. Heck we have the enterprise version here which includes StarTeam (one
of the best version control systems before Borland even bought it) and they
wont change from TeamSource. The teamsource that gets regular corruptions
and we are now on our 4th archive in 18 months.

> Not all tools are built equal, neither are all brains.

Very true

> I'm glad you think I'm quote worthy. :) maybe I'll go into a book.
> It's a funny assumtion to make that I may or may not have clients, 
> and that the code may or may not be a million lines of code? 
> Perhaps a million lines of code with plenty of issues, given the 
> right brain, rather that a lifecycle tool, would only be 100,000 
> lines of code, which lots less bugs.

If you can effectively managed bug reports, change requests and requirements
in your head for a large project, good luck to you. The ALM tools are for
everyone but are more suited to larger development teams. There are plenty
of alternatives around as well, some every free and open source.

How do you manage the bug reports and change requests currently? Are you
using another tool for it?