Right place for specific technical feedback?
-
Hello!
I'd like to share feedback on some specific technical aspect of Qt which looks as deficiency to me. What would be the right place for it, this forum or bug tracker?
To be more specific, I'd like to talk about some specific cases of error handing in QML and QML-native metacalls.
-
Hi
This is a user-driven forum so it's unlikely that any devs will see it.
So an enhancement bug report seems like a better idea.
You should/could add a link here so people can go and read and vote on your suggestions. -
Hi
This is a user-driven forum so it's unlikely that any devs will see it.
So an enhancement bug report seems like a better idea.
You should/could add a link here so people can go and read and vote on your suggestions.@mrjj said in Right place for specific technical feedback?:
Hi
This is a user-driven forum so it's unlikely that any devs will see it.
During dark ages of software development it was common to let the user "test drive" the new stuff.Such "policy" was never openly advertised, usually masqueraded as "beta testes wanted ".
Nowadays there seem to be no interest of "developers" to actively check that "masses" are still "test driving " THEIR software , by actually using it in real world and during such usage of THEIR software are still finding bugs.
IMHO it is ludicrous to expect the user to "file a bug" which in many cases should have been caught by QA .
But on the other had, I have been told few times -"what do you expect for free (software) ? Quality ? "
I realize my opinions are not in line with "everything Qt is cool " however, in such case I recommend to read "Inmates are running the asylum."
So an enhancement bug report seems like a better idea.
You should/could add a link here so people can go and read and vote on your suggestions. -
@mrjj said in Right place for specific technical feedback?:
Hi
This is a user-driven forum so it's unlikely that any devs will see it.
During dark ages of software development it was common to let the user "test drive" the new stuff.Such "policy" was never openly advertised, usually masqueraded as "beta testes wanted ".
Nowadays there seem to be no interest of "developers" to actively check that "masses" are still "test driving " THEIR software , by actually using it in real world and during such usage of THEIR software are still finding bugs.
IMHO it is ludicrous to expect the user to "file a bug" which in many cases should have been caught by QA .
But on the other had, I have been told few times -"what do you expect for free (software) ? Quality ? "
I realize my opinions are not in line with "everything Qt is cool " however, in such case I recommend to read "Inmates are running the asylum."
So an enhancement bug report seems like a better idea.
You should/could add a link here so people can go and read and vote on your suggestions.@AnneRanch
Hi
Its not a "policy". Just a fact of life.
The Qt Developers hang out at the mailing list.
Not here.
Besides a forum is not really suited to keep track of bugs in the same way a dedicated bug tracking system is.IMHO it is ludicrous to expect the user to "file a bug" which in many cases should have been caught by QA .
But that is how the real world works.
Software does get tested before release but in case a user stumbles on a bug, its
is required to gain all information about how to reproduce the bug and that is what
https://bugreports.qt.io/secure/Dashboard.jspa is for. -
@AnneRanch
Hi
Its not a "policy". Just a fact of life.
The Qt Developers hang out at the mailing list.
Not here.
Besides a forum is not really suited to keep track of bugs in the same way a dedicated bug tracking system is.IMHO it is ludicrous to expect the user to "file a bug" which in many cases should have been caught by QA .
But that is how the real world works.
Software does get tested before release but in case a user stumbles on a bug, its
is required to gain all information about how to reproduce the bug and that is what
https://bugreports.qt.io/secure/Dashboard.jspa is for.@mrjj said in Right place for specific technical feedback?:
is required to gain all information about how to reproduce the bug and that is what
We are obviously getting into language semantic.
It may be "required" to gain better understanding of the issue , but it is something a user SHOULD decide how much of "required" info he is willing to provide. Check out "bugzila" for " well known" IDE and you be surprised how much "required" info they are asking for.
The "bottom line is , IMHO, if there is an issue - bug or improvements - it is to mutual benefits to developers and users to solve it - fifty fifty.
From years of experience - it looks as user is 80 and developer 20.Enough silly statistics , hope the OP did not get discouraged by "all this talk".
Thunder is good, thunder is impressive; but it is lightning that does the work.
Mark Twain
