On 01/ 7/11 04:07 PM, Nathann Cohen wrote:
Could the ticket creator be granted the right to close it ? It happens
really often that I create a ticket, then write the actual patches weeks
(months) afterwards, having long forgotten about the first ticket.
Alternatively, when a patch is written as a part of another one....
Well, if we have the right to create tickets, shouldn't we be granted the
right to close (at least) ours ? ^^;
Nathann
I've seen cases where
1) Person A opens a ticket for a problem.
2) Person B tells them a work-around. It might need root access, or something
else that we don't want Sage users to require.
3) Person A is happy with the work-around, so would then close the ticket. But
really the underlying problem has not been solved.
I've seen the above with a ticket about ATLAS build issues. Someone closed the
ticket, even though the underlying reason for the problem has not been resolved.
So I'm not so convinced it is a good idea to let the original person close the
ticket.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
