Could you define “forever”, have you looked at the top 18 lately? Ranging from 12 years to 4 years.
Push all that.
I think the fact that people voted should indicate their desire? Or is voting just the illusion that we’re thinking seeing it is?
2 Likes
As I outlined on the case, cases have to be specific so that (a) we know we met the criteria of the case so that it can be closed and (b) so that others voting for it know what they are voting for. The case description was so vague that there’s no way that criteria would be met.
It’s that simple. I don’t have a problem with the concept but the case has to be specific enough for us and for those that are voting for it. Otherwise, everyone will decide in their own minds what the definitions are and no two are likely to be the same.
It’s also important to remember that we fixed 161 bugs in r1.
Well, I cant even see the case because feedback.
Can somebody please post the details so we can have a look?
Never mind, I found it elsewhere.
About 130 of which were discovered or introduced in recent releases and 12 that were fixed by virtue that web1 was replaced which leaves around 20 long term bugs fixed in around 6 months.
7 Likes
I have 398 reviewed cases (in my cases list) and 12 reproducible cases.
I have only 5 top things to can put my points on.
and you should know that any issue against the plugin SDK affects more or less all my plugin customers, e.g. a 1000 Pro licensed users!
Even my thread of patience is not endless.
7 Likes
I, as many more i assume, am SICK of the current behaviour of Xojo Inc.
We will continue to monitor the progress Xojo makes within the next 6 Month and then decide how to proceed.
We are in the lucky position that we can work with the current Xojo Releases on a single Windows 10 Machine without any major showstoppers and we needed Xojo only for 1 big project. I stopped developing with Xojo as my hobby and started to learn something new…
3 Likes
Well, that idea was killed fast! 
No feedback point system in the world will ever fix Xojo’s Bug Problem if they don’t want to see it. I wonder if this feedback smokescreen is meant for us users or to ease their own minds? I guess if you keep saying to yourself ‘there is no problem’, you just will eventually start to believe it. If a feedback suggestion like ‘Snow Leopard’ raises to the top 10 place in a matter of hours, the community is trying to say something. Shooting it down will not remove the problem.
Refusing the help of pro 3th party devs like @Christian_Schmitz (who is actually the ‘bug-fixer’ and savior of Xojo in many cases) is just incomprehensible. Nobody will think less of Xojo because they admit: ‘Guys, we can’t see the horizon anymore over this pile of bugs. We need help’!
Never seen a company so being in denial. It is sad really…
I think you forgot to add the new bugs introduced in this new release. Pretty sure we are back in the red now… 
3 Likes
I just looked at the Top 20. Only two are bug reports. The rest are feature requests. It would be interesting to see a filtered list showing just the Top 20 bug reports. And then, maybe a clearly defined Feedback case could be opened: Do a release fixing only the specific “Top 20” bugs shown for a single release, listing those items. If the Top 20 changes after the report is created, too bad, it’s locked in but people can still vote on that set / group.
There could even be “an open season” on voting for bugs, where people are encouraged to remove all feature requests from their Top 5, and rank only bug for a week before the report is submitted in stone.
Once the “open bug hunting season” is done, the top 20 is put into the report. And people can vote on the group proposal if they want a release to focus ONLY on those specific top 20 bugs.
If not enough of your bugs are in the top 20, don’t vote for it – Unless you feel the Xojo community would still benefit from it and you can wait 6 months for your bugs and/or features requests to come after.
Honestly, this sounds fun in a way. But also a bit silly. Can we get 400,000 users to agree on anything?
I remember many years back where the #1 and #2 reports were contradicting each other. I don’t recall what it was, but something like “#1 Add iPhone support” and “#2 Don’t waste time adding iPhone support”. 
It seems clear to ME the number of people using feedback is much, much, much smaller than that. Within a few hours of being created a case just made it to the top 20 (10?), probably by getting the points from just a handfull of xojo users. This makes me doubt of the representativeness of that system. Moreover, as I understand Geoff’s message, the rank is used as an indicaiton of the “impact surface” of the bugs, but with such a low participation (if my previous conclusion is right) the rank loses all meaning.
The case that was closed a few hours ago asked for bug fixes for a couple of releases, not to stop all development of new features for the future. They are perfectly compatible (unlike the requests of your example/anecdote).
In response to Geoff’s explanation of why the case was closed, in my opinion that case was perfectly clear and defined: fix as many bugs as possible in the next two releases. You have always decided which bugs to fix without the guidance of the users, why would you need the case to specify which bugs need fixing now?
Julen
3 Likes
There’s a new Feedback case (currently ranked 17th) that simply asks Xojo to analyse the top 200 verified and reproducible bugs and strive to fix them in a new release. Just rank the reproducible bugs and fix them in rank order. Is that specific enough?
2 Likes
Well the point I was trying to make is that if a couple of bug fix releases cause a delay in the release of new features or other pressing things, like Apple Silicon support, even 3-6 months delay may be enough to cause some to vote for that NOT to happen, and just keep the schedule as it normally is. (e.g. “#1 Do a bug fix only release” vs. “#2 Keep the schedule the same”) Not saying that will happen, just I’ve seen it happen before in Feedback.
Both serious and sarcastic depending on what you’re getting at. I pulled 400K directly from Xojo’s home page, but I was not actually suggesting 400K use Feedback – Or that they’re all paying users with “feedback voting rights” (I assume a decent percentage of that is free/Linux, Lite, etc.)
I was simply making a point that there’s a lot of user’s opinions to be considered, and I find it interesting that as of this writing, the Top 20 only has only 2 bug reports (well 3 if you count the new “do a bug fix release”), and none in the Top 10.
Curious, I wonder how many users who want the bug fix release still have feature requests in their Top 5 right now? Maybe they should remove all feature requests from their Top 5 to drive up more of those individual bugs into the top 20!
You ARE aware that bug reports by their very nature are singular (eg you may never encounter the bug I’m struggling with, eg if you don’t use RegEx then you won’t face Regex bugs) while feature requests are cumulative (“Who wants Xojo for iOS? EVERYONE!”).
After all, I said it often enough, so it IS disappointing when people seem to think that bugs and features are equally weighted in the feedback system … 
3 Likes
You have the “Need information” status for that, where the user has 10 days to add information. Here, closing the case without wanting more information implies you don’t want to listen to that. My two cents.
6 Likes
Of course. Well mostly. Some are singular, others effect more people. This is why I wish there was a way to see a filtered list of the Top 20 bugs only. That would be interesting for sure and may help shine light on what is affecting the most people, which the “bug fix release” is all about right?
I don’t know how many times we’ve filed a bug report without adding it to one of our 5 point slots… This points system is not working well…
1 Like
I’ve argued for years that bugs and feature requests have to be listed separately. My impression is that Xojo wants it as is because it allows the claim that users “want” features …
3 Likes
I know quite a few people who have many more bug reports than the five available places … after a while you just give up. What’s the point when you have 20 verified bugs and nothing has happened for years … why even report number 21? [and I tip my hat to Norman who has a LOT more bugs reported …]
6 Likes
Exactly, you just don’t do then. And one day you leave… 
4 Likes
Maybe the point/rank system could be split into two sections: Features and Bugs. You get the standard points for features that we have today. Assign them to Top 5 or whatever. But for Bugs… well, no points at all. You simply rank them in order. If you have 200 bug reports, well just rank them any way you want! Then Xojo can tabulate your Top X bugs with everyone else’s Top X bugs, and come up with a master list of top bugs.
Then… we have two separate Top 20 lists we can view as well.
1 Like