On 10.10.2017 17:03, Roland Hughes wrote:
>
> If YOU need a copy of something which clearly will not fit within the
> confines of the bug tracker system YOU take the additional time to
> copy it.
>
> Turning your argument around, what happens when your current bug
> tracking system disappears and
It's a bad practice and they have disabled replies.
"Needs more info" is the universal cry of "I don't want to do it now."
Having been in IT over 30 years and worked at countless shops as a
consultant, I've seen that one used first hand to facilitate doing
nothing. I've seen it used on bug rep
It is totally reasonable to provide a link to a post with far more
content than the bug tracking system can contain. If they, whoever they
are, feel the need to replicate data then they should replicate the
portion they actually worked on.
This bug is a shining example of the failure of AGILE
If YOU need a copy of something which clearly will not fit within the
confines of the bug tracker system YOU take the additional time to copy it.
Turning your argument around, what happens when your current bug
tracking system disappears and is replaced by something else? You
_still_ lose the
On 10/9/2017 2:30 PM, Giuseppe D'Angelo wrote:
Il 09/10/2017 21:37, Roland Hughes ha scritto:
While we are on the topic, here is the lovely response.
http://www.logikalsolutions.com/wordpress/wp-content/uploads/2017/10/Screenshot_20171009_143236.png
No Sir By God! Not gonna look at a blog p
On 10/10/17 06:37, Roland Hughes wrote:
While we are on the topic, here is the lovely response.
Be reasonable.
Just linking to your rambling blog in the bug report is not reasonable.
Hamish
___
Interest mailing list
Interest@qt-project.org
http:/
Il 09/10/2017 21:37, Roland Hughes ha scritto:
While we are on the topic, here is the lovely response.
http://www.logikalsolutions.com/wordpress/wp-content/uploads/2017/10/Screenshot_20171009_143236.png
No Sir By God! Not gonna look at a blog post with screen shots and
everything in it. Wants
While we are on the topic, here is the lovely response.
http://www.logikalsolutions.com/wordpress/wp-content/uploads/2017/10/Screenshot_20171009_143236.png
No Sir By God! Not gonna look at a blog post with screen shots and
everything in it. Wants it cut & pasted into a text only box.
And they
- schedule a triage week every couple of months to go through the current
backlog and reassess/re-prioritize? (again, don't know if this is done -
doesn't seem like it from the outside)
This should maybe also include the bugreports whose assignee went missing
years ago and are just stalled (or w
On 10/07/2017 05:15 PM, interest-requ...@qt-project.org wrote:
On Saturday, 7 October 2017 14:58:03 EDT Andy wrote:
I don't really want to play the "pile on" game (and sorry for hijacking
the
current thread), however as someone who cares about Qt and has been using
it for a long time this is
On Sat, Oct 7, 2017 at 4:11 PM, Thiago Macieira
wrote:
> On Saturday, 7 October 2017 14:58:03 EDT Andy wrote:
> > I don't really want to play the "pile on" game (and sorry for hijacking
> the
> > current thread), however as someone who cares about Qt and has been using
> > it for a long time this
On Saturday, 7 October 2017 14:58:03 EDT Andy wrote:
> I don't really want to play the "pile on" game (and sorry for hijacking the
> current thread), however as someone who cares about Qt and has been using
> it for a long time this is a particular source of real frustration.
>
> Bug reports often
On Saturday, 7 October 2017 13:27:50 EDT Krzysztof Kawa wrote:
> I don't want to be mean Thiago, because I love Qt, I do appreciate
> your hard work and all the people that make it happen, but you need to
> consider that you're pretty big part of Qt and things around you do
> move in a different pa
I don't really want to play the "pile on" game (and sorry for hijacking the
current thread), however as someone who cares about Qt and has been using
it for a long time this is a particular source of real frustration.
Bug reports often get labelled as "Reported" and then ignored (the
"priority" on
I don't want to be mean Thiago, because I love Qt, I do appreciate
your hard work and all the people that make it happen, but you need to
consider that you're pretty big part of Qt and things around you do
move in a different pace. It's not the same for some of us.
As an example consider this P2 bu
On Saturday, 7 October 2017 05:49:00 PDT Roland Hughes wrote:
> I expect, like all OpenSource bugs, it will be ignored until the version
> it is reported against is no longer supported, then it will become a
> "closed" bug.
Except for all the bugs that I close, which are only about the open source
Bug filed.
https://bugreports.qt.io/browse/QTBUG-63650
I expect, like all OpenSource bugs, it will be ignored until the version
it is reported against is no longer supported, then it will become a
"closed" bug.
Thanks for the reporting link though.
On 10/05/2017 05:11 PM, Irfan Omair wrote
The link is in the blog post. Actually, both links are. Look for
"official Qt Wiki article"
On 10/05/2017 05:11 PM, Irfan Omair wrote:
You can always log a bug here:
https://bugreports.qt.io/
What page of wiki you are referring here is wrong?
On Thu, Oct 5, 2017 at 3:03 PM, Roland Hughes
ma
You can always log a bug here:
https://bugreports.qt.io/
What page of wiki you are referring here is wrong?
On Thu, Oct 5, 2017 at 3:03 PM, Roland Hughes
wrote:
> All,
> Rather than pollute the list with a ton of pasted stuff which causes it to
> needlessly send countless digest messages, I hav
All,
Rather than pollute the list with a ton of pasted stuff which causes it
to needlessly send countless digest messages, I have included all of the
information in this blog post.
http://www.logikalsolutions.com/wordpress/information-technology/how-far-weve-come-pt-18/
I have 2 questions:
1
20 matches
Mail list logo
