In a discussion at the sprints today Nick observed that 'invalid' was a resolution that carried a rather negative subtext ("your bug report was invalid", ie: "you made a mistake") , and that Red Hat used 'not a bug', which we all agreed was much more descriptive of the actual resolution.
So, I've changed the text associated with the 'invalid' resolution to read 'not a bug' instead.
--David
On Tue, Apr 15, 2014 at 9:45 PM, Ethan Furman ethan@stoneleaf.us wrote:
Any chance of changing the 'committed/rejected' text to something else? :)
Good that you brought this up. It always feels confusing to me.
My suggestion is: Let's have committed for stuff that is committed
Not committed for stuff that is not a bug.
:-)
On 15 Apr 2014 22:37, "Senthil Kumaran" senthil@uthcode.com wrote:
On Tue, Apr 15, 2014 at 9:45 PM, Ethan Furman ethan@stoneleaf.us wrote:
Any chance of changing the 'committed/rejected' text to something else?
:)
Good that you brought this up. It always feels confusing to me.
My suggestion is: Let's have committed for stuff that is committed
Not committed for stuff that is not a bug.
Brett & David are working on a more general review of the tracker experience. This was just a quick & easy change to get things started :)
Cheers, Nick.
:-)
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
On 4/15/2014 9:45 PM, Ethan Furman wrote:
On 04/15/2014 05:55 PM, R. David Murray wrote:
[...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...]
Nice.
Any chance of changing the 'committed/rejected' text to something else? :)
Like 'finished'? 'completd'? 'done'? or even 'closed'?
On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy tjreedy@udel.edu wrote:
On 4/15/2014 9:45 PM, Ethan Furman wrote:
On 04/15/2014 05:55 PM, R. David Murray wrote:
[...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...]
Nice.
Any chance of changing the 'committed/rejected' text to something else? :)
Like 'finished'? 'completd'? 'done'? or even 'closed'?
Yes, dealing with committed/rejected, and indeed the whole stage/status workflow, is on the list to be addressed.
It is very redundant to have to set both 'closed' and 'committed/rejected', so one suggestion, that we could implement right away, would be to simply delete that option, and then status gets left at 'commit review' when the bug is closed. (Or if you don't like that you could put it back to unset.) Later I think we may want to merge status and stage, but we'll consider that as a part of a bigger review of the workflow.
--David
On Wed, 16 Apr 2014 10:53:53 -0400, "R. David Murray" rdmurray@bitdance.com wrote:
On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy tjreedy@udel.edu wrote:
On 4/15/2014 9:45 PM, Ethan Furman wrote:
On 04/15/2014 05:55 PM, R. David Murray wrote:
[...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...]
Nice.
Any chance of changing the 'committed/rejected' text to something else? :)
Like 'finished'? 'completd'? 'done'? or even 'closed'?
Yes, dealing with committed/rejected, and indeed the whole stage/status workflow, is on the list to be addressed.
As an immediate improvement (pending further work) I've changed the label from 'committed/rejected' to 'resolved'.
--David
On 04/18/2014 07:31 PM, R. David Murray wrote:
On Wed, 16 Apr 2014 10:53:53 -0400, "R. David Murray" rdmurray@bitdance.com wrote:
On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy tjreedy@udel.edu wrote:
On 4/15/2014 9:45 PM, Ethan Furman wrote:
On 04/15/2014 05:55 PM, R. David Murray wrote:
[...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...]
Nice.
Any chance of changing the 'committed/rejected' text to something else? :)
Like 'finished'? 'completd'? 'done'? or even 'closed'?
Yes, dealing with committed/rejected, and indeed the whole stage/status workflow, is on the list to be addressed.
As an immediate improvement (pending further work) I've changed the label from 'committed/rejected' to 'resolved'.
Many thanks!
-- ~Ethan~
On 4/15/2014 8:55 PM, R. David Murray wrote:
In a discussion at the sprints today Nick observed that 'invalid' was a resolution that carried a rather negative subtext ("your bug report was invalid", ie: "you made a mistake") , and that Red Hat used 'not a bug', which we all agreed was much more descriptive of the actual resolution.
So, I've changed the text associated with the 'invalid' resolution to read 'not a bug' instead.
Thank you. I have usually looked for something else to use ;-).
participants (5)
-
Ethan Furman -
Nick Coghlan -
R. David Murray -
Senthil Kumaran -
Terry Reedy