Robert Bradshaw wrote:
On Mar 11, 2010, at 12:04 AM, Alex Ghitza wrote:
On Thu, 11 Mar 2010 18:42:00 +1100, Minh Nguyen
<nguyenmi...@gmail.com> wrote:
Third, in many cases, one can open a new ticket to improve the changes
introduced by a patch from an existing ticket. In such cases, I think
one can suggest this option to the patch author and leave it to them
to either incorporate the changes in the current patch, or to open a
new ticket to implement the change.
In my experience, "resolving" issues with a current ticket by opening a
new ticket results in sub-par code getting in--and the motivation to
make improvements drops substantially (meaning the follow-up tickets can
linger for a long time).
I agree with Robert there. It is better the code is committed with issues
resolved, rather than leave them for a later date.
Of course it depends on the nature of the
suggested changes--it's a good idea to push unimplemented enhancements
off to new tickets, but not defects.
Obviously.
- Robert
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
