I'm confused about exactly where we should report / track bugs.

Solar2D General Questions/Discussion
#1

There is a sticky on this forum, with a link that takes you to something called fogbugz. I’d never heard of it before, but registered for it and saw that there were a loads of bugs reported there.
However last week I submitted a bug using the “Report a Bug” tab at the top of the screen. I assumed that was the correct way to do it, since it’s right here on Corona’s website.
I can’t see anywhere in my account details to track whether anything is being done with this bug report, and it was not listed on the fogbugz page, but I did get an email confirming it had been received and entered onto your tracking system.

So exactly how do we check the status of reported bugs? [import]uid: 84115 topic_id: 31756 reply_id: 331756[/import]

#2

Incidentally if anyone from Ansca looks at this, the bug in question is “Case 17857: Open AL Pitch shifting not working correctly on Android”.
I reported the bug myself, though my boss is a corona subscriber so I don’t know if it can be given higher priority if he confirms this since the bug is affecting our whole project? [import]uid: 84115 topic_id: 31756 reply_id: 126773[/import]

#3

Fogbugz is an Open Source bug tracker, but IMHO It’s practically useless to us.

You are right to post your bug through the “Report a Bug” at the top. You are given a number that will show up in FogBugz, but you can’t search on it very well. There is another string you need to search on and once there you are very restricted about what you can see. FogBugz is quite frustrating.

However, when you report a bug, Corona Labs is pretty good about emailing you when they do look at your bug and you can reply via email and those replies stick with the bug.

You of course can post in the forums, but it’s hit and miss if Corona Labs will look at it and its really more of a place for the community to take a crack at solving your problem. Once you have a reproducible bug that you can demonstrate in a simple app, then you can file the bug with the link at the top of the page and Corona Labs does a very good job of addressing those bugs. But like any system, these turn into development tickets and end up in something called the “Backlog”. Its should not be deemed a negative term, but its simply the list of things that needs worked on. They prioritize them and pick out what they can work on in addition to features that we are also begging for and that’s what goes into their work cycle.

We have to be patient and let them get things done. If they rush, there will be even more bugs.

[import]uid: 19626 topic_id: 31756 reply_id: 126851[/import]

#4

Incidentally if anyone from Ansca looks at this, the bug in question is “Case 17857: Open AL Pitch shifting not working correctly on Android”.
I reported the bug myself, though my boss is a corona subscriber so I don’t know if it can be given higher priority if he confirms this since the bug is affecting our whole project? [import]uid: 84115 topic_id: 31756 reply_id: 126773[/import]

#5

Fogbugz is an Open Source bug tracker, but IMHO It’s practically useless to us.

You are right to post your bug through the “Report a Bug” at the top. You are given a number that will show up in FogBugz, but you can’t search on it very well. There is another string you need to search on and once there you are very restricted about what you can see. FogBugz is quite frustrating.

However, when you report a bug, Corona Labs is pretty good about emailing you when they do look at your bug and you can reply via email and those replies stick with the bug.

You of course can post in the forums, but it’s hit and miss if Corona Labs will look at it and its really more of a place for the community to take a crack at solving your problem. Once you have a reproducible bug that you can demonstrate in a simple app, then you can file the bug with the link at the top of the page and Corona Labs does a very good job of addressing those bugs. But like any system, these turn into development tickets and end up in something called the “Backlog”. Its should not be deemed a negative term, but its simply the list of things that needs worked on. They prioritize them and pick out what they can work on in addition to features that we are also begging for and that’s what goes into their work cycle.

We have to be patient and let them get things done. If they rush, there will be even more bugs.

[import]uid: 19626 topic_id: 31756 reply_id: 126851[/import]