Hi Walter,
actually I think the issue tracker is great, but not how you use it. If you guys would use it in a usual way, then it is transparent. Right now it is not. People post here in the hopes that it will be noticed, which I doubt it is at a 100% rate. People post on the tracker but you close the issue, move it somewhere else. This is untransparent. There is no further communication between the user and the developer.
You should get rid of your internal list. The only thing the user gets out of this list is the track id, which rose big time over the last 4 months. Which is kinda worrying to me.
Now and while I am at it…
Same goes for your roadmap. For a long period it was what was promised to the users. Even with quartly ETA’s. Some of these users supported you guys for quite a while and where thinking that you guys stick to it.
Then all of a sudden and by Carlos words, the roadmap got “lost”. How? A Ninja sneaked into AM’s office and stole it? Or someone accidently put it into the trash and the cleaning service brought the bin out a day to early?
Common, I can fool myself much better. I think you guys simply didn’t wanna be held to that list. You promised something you can’t deliver, or don’t want to anymore.
Over the months I got this picture from AM and some staff here. A lot of talk and no action. Or a veeeerrrryyyyy slooooow action. You guys are great when it comes to pitching Corona and making sales. When a former competitor struggles you send your armies out to collect the wealth and smear honey around their users mouths to make it look like you are all just there to help about their problems.
But on the support side of your current users you lack big time. I still can’t understand and see that some crucial bug fixes like the OpenFeint archievement bug or the Android physic/framerate bug take so much time to fix.
To me it looks like you have one codebase that you work on. There you fix bugs and implement new features. So if you have a crucial bug, people have to wait till you think a new release is worth it to be shown to the public. Btw, just renaming the Openfeint implementation is not a new feature.
Imho how you handle bugfixes is the way the big players like Adobe work. No wonder that you guys choose this method as you worked there before. But it is a very bad way.
You should have a codebase where you fix bugs and which could be released inbetween. Send the fix out to the users right away. People are depending on Corona for their apps and that Corona works as advertized. We are waiting now almost 2 months for official bug fixes of these mentioned problems! Hello!?!?!?
Then these bug fixes would be integrated into the codebase for the next release which includes new features.
Corona is an awesome concept. Limited but easy to grasp and work with. Right now you guys are a trend. But so were GarageGames one day.
Sorry about the offtpic rant, I am just feed up with promises which are not lived up to. I had raised my voice before about these things and I said I would not do it again. But I guess after I had contacted Carlos last week about some simple info I needed and which I didn’t got after 8 days waiting, I am very disappointed and feed up.
@Carlos: I don’t need that infomation anymore. Thanks for listening and I promise I won’t contact you again.
Btw. do we HAVE TO post our new corona based apps here on the board or is this optional. I am not sure If I understood that part of the Eula.
Over and out
Michael Hartlef
http://www.whiteskygames.com
http://www.twitter.com/mhartlef [import]uid: 5712 topic_id: 3609 reply_id: 10957[/import]
