Bug Tracking Software?

[voetsek]

when someone asks for help or even offers to help in any way, the response to a question should never be, cause thats the way it is or just because.

Originally Posted by voetsek

when someone asks for help or even offers to help in any way, the response to a question should never be, cause thats the way it is or just because.

Nobody sayd that, you arent reading what I wrote correctly.


You made a request, I stated that is the way it is, because it is ALREADY that way, there isnt a need for a change because its already done the way you were stating.

Last post on this issue because I think you are just out to cause issues on the forums and dont realy want help.

[JuViR]

1) Start, mostly working code that is current with live
2) Fix bugs or add features to this code -OR- Have to update everything to live
3) Internal testing
4) Release Development Releases(DRs) of the next version, typically have at the very minium walking around and zoning, but normally have 80% of previous feature set working and everything important working.
5) Continue updating to live or adding features AND fix bugs that are reported in a USEFUL way.
6) Spend plenty of time reading posts or trying to fix someone's issues and it turns out they screwed up and are using a bad database, or doing something stupid.
7) Reply to posts about people complaining about AAs not working right or pathing, state that we need people to packetcollect AAs and send us the logs and never receive any logs.
If ready with what we believe is a STABLE version that works with live and has 95% functionality, release new version
9) Goto 1

Welcome to the Basic programming language.