Found a bug?
Posted: Thu Nov 09, 2006 10:08 am
If you think you found a bug we would be happy to hear about it, really developers cant check for every possible combination of hardware / software and other stuff for every line they write. Well we could but then we couldn't release anything.
Forum is a great place to talk about possible bugs and maybe even find a way around it but its not good for informing developers about bugs. Most developers don't have time to read through the forum every day (which means that when they do there are 5-10 pages of unread messages and it would take the whole day to read them all)
Thats why we have forge and its bugtracker.
If you never looked at the forge now is a good time to check it http://dev.cmsmadesimple.org/
Now there are some things one needs to remember when submitting a bug, here is a short list of things one needs to remember when submitting a bug.
1. is this a bug?
- check that you don't abuse the program. CMSMS cant make you coffee so reporting a "cmsms makes lousy coffee" is not a bug
2. is your own system ok
- check that you have the right version of php, mysql/postgresql and so on
3. is this a new bug?
- check the bugtracker to see if someone has already submitted this bug, if yes you can add your comments in that bug and maybe some more information
now you know everything you need to file a bug report. Now a good bug report holds just the right amount of information.
1. Steps to reproduce
2. What you expected to see
3. What you saw instead
4. Software versions used (including apache php mysql versions)
Now after you have filed your bug devs that have marked them self as monitoring the bugtracker will get notified and when someone has time they will work with it. You will also get notified of the status changes of your own bugreport if you wish.
Some time passes and a dev marks the bug as fixed, now is your turn to check if the bug really is fixed. If yes then great, you can comment on the bug tracker that you can confirm this bug as fixed and someone will close that bug later. If not comment information of what happened.
In some rare cases fixing a bug introduces a new bug, this should also be commented on the original bug report and then open a new bug for the new problem.
Working like this might sound like too much for you, but when there are multiple persons developing, using and checking system there really needs to be a central place to file bugs.
and here is a nice article about bugs http://www.joelonsoftware.com/articles/ ... 00029.html
Thanks to everyone using CMSMS
Forum is a great place to talk about possible bugs and maybe even find a way around it but its not good for informing developers about bugs. Most developers don't have time to read through the forum every day (which means that when they do there are 5-10 pages of unread messages and it would take the whole day to read them all)
Thats why we have forge and its bugtracker.
If you never looked at the forge now is a good time to check it http://dev.cmsmadesimple.org/
Now there are some things one needs to remember when submitting a bug, here is a short list of things one needs to remember when submitting a bug.
1. is this a bug?
- check that you don't abuse the program. CMSMS cant make you coffee so reporting a "cmsms makes lousy coffee" is not a bug
2. is your own system ok
- check that you have the right version of php, mysql/postgresql and so on
3. is this a new bug?
- check the bugtracker to see if someone has already submitted this bug, if yes you can add your comments in that bug and maybe some more information
now you know everything you need to file a bug report. Now a good bug report holds just the right amount of information.
1. Steps to reproduce
2. What you expected to see
3. What you saw instead
4. Software versions used (including apache php mysql versions)
Now after you have filed your bug devs that have marked them self as monitoring the bugtracker will get notified and when someone has time they will work with it. You will also get notified of the status changes of your own bugreport if you wish.
Some time passes and a dev marks the bug as fixed, now is your turn to check if the bug really is fixed. If yes then great, you can comment on the bug tracker that you can confirm this bug as fixed and someone will close that bug later. If not comment information of what happened.
In some rare cases fixing a bug introduces a new bug, this should also be commented on the original bug report and then open a new bug for the new problem.
Working like this might sound like too much for you, but when there are multiple persons developing, using and checking system there really needs to be a central place to file bugs.
and here is a nice article about bugs http://www.joelonsoftware.com/articles/ ... 00029.html
Thanks to everyone using CMSMS