Implement a public bug reporting and status program

[RobertJay]

I believe the platform has reached the complexity (from Appery's perspective) level and number of users and reported issues to require a dedicated public bug reporting and status system. It would allow users and Appery support personnel to save enormous time e.g by reducing redundant, wasteful and off-target forum and support email postings. In my opinion, using Get Satisfaction's fairly-weak search mechanism on these forums is a far less productive and professional way of dealing with this. Information in the current email support system is private and does no good for the community at large. Knowing the status of bugs would be of great help in planniing for developers working with their clients or on their own projects.

[Alena Prykhodko]

Hello,

We have a list of commonly faced issues here https://devcenter.appery.io/known-iss..., workarounds for some of them and we update status of the issue once it's fixed.

[RobertJay]

Alena, thank you, but that's a pretty useless resource. It does not include anything close to all reported and accepted bugs and indicates that the last reported bug fix was seven months ago (which I hope and presume is laughably out-of-date). And very importantly, it does not include any indication of a bug's status to help developers do their jobs for themselves and clients.

[Alena Prykhodko]

Dear Robert,

For now this information is only for internal use, we do not plan to make it public. That's why the doc above was created, we post here general bugs and problems.
If you need to know status of specific issue let me know.

[RobertJay]

That's obviously very disappointing and something I think is a bad mistake for Appery and bad news for its users. I'd be curious as to your rationale.

[RobertJay]

Alena, a month ago Appery mentioned in the following it was working on a bug where the before load event did not work. Has that been fixed?

https://getsatisfaction.com/apperyio/...

[Alena Prykhodko]

Dear Robert,

We plan to fix this bug in upcoming release.

[RobertJay]

Thank you very much