EQEmulator Forums

EQEmulator Forums (https://www.eqemulator.org/forums/index.php)
-   Archive::Bugs (https://www.eqemulator.org/forums/forumdisplay.php?f=622)
-   -   Bug Tracking Software? (https://www.eqemulator.org/forums/showthread.php?t=11112)

voetsek 12-31-2003 03:03 AM

Bug Tracking Software?
 
Could we use a bug tracking software instead of posting stuff to this forum?

I think this would make it very easy for people to see exisiting problems, and get code for solutions to their problem.

Secondly, a cvs is needed.

Here is an example of a free bug tracking software that could be used. hell, i'd even host it, doesnt matter, just something is needed.

http://flyspray.rocks.cc/demo/

find others at http://www.hotscripts.com I can host ASP, PHP, MySQL, and MS SQL.

Trumpcard 12-31-2003 03:43 AM

It would be a nice idea, but we're too decentralized from a development standpoint to do it.. Who's going to assign tickets, how do you ensure everyone uses it, etc..

We have a cvs.. Its just not accessible to the general public. We did use souceforge but have discontinued recently due to issues with their support. We're investigating alternatives but lets face it, its the holidays, this is the slow time of the year for everyone so its not been a priority...

voetsek 12-31-2003 03:53 AM

http://www.northarc.com/bugtrack/

there u go.

its not really about assigning bugs, just hosting solutions to common problems.

i just look through the forums for find fixs for problems in various places.

voetsek 12-31-2003 07:57 AM

Quote:

Originally Posted by Trumpcard
It would be a nice idea, but we're too decentralized from a development standpoint to do it.. Who's going to assign tickets, how do you ensure everyone uses it, etc..

We have a cvs.. Its just not accessible to the general public. We did use souceforge but have discontinued recently due to issues with their support. We're investigating alternatives but lets face it, its the holidays, this is the slow time of the year for everyone so its not been a priority...

why no public access to cvs ? it would be alot easier on people who run servers if they had access to that.

mattmeck 12-31-2003 08:18 AM

Quote:

why no public access to cvs ? it would be alot easier on people who run servers if they had access to that.
Imagin all the people who spam the bord trying to get there server to work. You know the ones who ask questions that are already answered in the thread right below theres? Now imagin them having access to the unfinished product, there would be millions more support questions.

I know they have a list of other reasons but that is the first I think of.

voetsek 12-31-2003 08:39 AM

well, i can see your point, but wouldnt there be two versions of the code. dev copy and a stable copy. stable has all the latest fixes, like mob hp, ld on death, etc etc.

mattmeck 12-31-2003 09:15 AM

thats the way it is 8)

voetsek 12-31-2003 06:18 PM

Quote:

Originally Posted by mattmeck
thats the way it is 8)

you may think its cool cause you can say that, but to tell you the truth, that is why people get pissed off and dont want to help at all. why bother helping if your just told, that the way it is.

im not suprised at all that people leave this project like krusher, makes perfect sense now.

thanks for being real supportive.

Edgar1898 12-31-2003 06:44 PM

I think thats a good idea, if people are willing to post their bugs there then it would definately be a lot easier to track. If you still want to do this make a post that explains how to add a bug using that interface and basic functions of the interface and I'll make it a sticky. Please try to be as thorough as possible, some users arent as computer savy as some of us are :P

kathgar 12-31-2003 06:54 PM

We used Sourceforge's Bugs and Tasks(when sourceforge worked well) and people just stopped using them. We had BugZilla, no one used it. We have a -private- cvs, that we cannot give access to everyone. That is why we set up a bidaily export to a public CVS for everyone. The problem is we used sourceforge's CVS and it's screwed up. We do NOT however need people running CVS code if they do not know what they are doing. You see the guides that give CLEAR STEP BY STEP instructions for compling from cvs? Yeah well there are tons of questions about people that cannot even get cvs setup to begin with. Those are not generally the kind of people that will a) report bugs in a way that is USEFUL (omg it not work fix it plz!!!111). or b) able to fix the bugs themselves. If you would even read trumpcard's post he said the same thing.

I will explain our development cycle, and other issues as best I can.

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.
8) If ready with what we believe is a STABLE version that works with live and has 95% functionality, release new version
9) Goto 1

voetsek 12-31-2003 07:29 PM

Is running a Development and stable cvs too much work ? if it is, i understand.

Edgar1898, ill throw some instructions tomorrow how the thing works and how to link to it and everything. since i started my own server, people ask the same things over and over, and i know others who run their server get asked the same thing. with the bug track, i just want a 1 spot stop for anything bug related just so its documented and known.

kathgar 12-31-2003 11:32 PM

You are going to need to define what you mean by the stable and devel CVSs. If you mean STABLE to be the code we have when we release a new version(stable code) that isn't needed.. it's on sourceforge. If you mean release + bugfixes that would serve little purpose?

voetsek 01-01-2004 04:22 AM

Here is a simple howto file bug reports.

http://www.northarc.com/bugtrack/

Logging a New Bug -
Click Open a new Task anonymously

Add a summary of your bug, select which server type and version if known you found the bug in, add a detailed description in the details field.

Click Add this task.

---------

TO be able to track your bugs, or your a developer then register a new account and an autorization code will be emailed to you. Once you get this, please email voetsek@northarc.com if you need higher access to work the bugs. If you register, you can track updates to the bugs you submit.

Develoers can assign tasks if they want, set the percent complete of a task and edit the category or task type.

To upload scripts, compiled code, etc you must register an account.

--------

Searching for answers -

Use the search field and select all statuses for tasks and you will find open and closed bug reports that hopefully contain your answer.

devn00b 01-01-2004 05:52 AM

We have comercial software avail atm (TestTrack Pro), I could set it up np but as been stated before, i dont think anyone will use it.

mattmeck 01-01-2004 06:33 AM

Quote:

you may think its cool cause you can say that, but to tell you the truth, that is why people get pissed off and dont want to help at all. why bother helping if your just told, that the way it is.

im not suprised at all that people leave this project like krusher, makes perfect sense now.

thanks for being real supportive
wait just a darn second, when i stated
Quote:

thats the way it is
I was stating that everyone CAN access the latest stable code(asuming they can compile) I think you need to have a beer / take a chill pill befor you freek out and try to make yourself look like a victom. nuff sayd.


All times are GMT -4. The time now is 12:22 PM.

Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.